Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fe3dc29f89a39c79992b087137b86602490ca2ebbce3cbe1d36f3ee1aac9c8ff

Tx prefix hash: 7192a1f3825beb4ccbb8f5a6985c9057bd625612a33b2096d2e451a0f3b51633
Tx public key: f3e37d00104a565e451cea9ee8f6b3469d57e42f0796ef95922c866dd0c116a4
Timestamp: 1710357434 Timestamp [UCT]: 2024-03-13 19:17:14 Age [y:d:h:m:s]: 01:019:12:30:22
Block: 977637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274914 RingCT/type: yes/0
Extra: 01f3e37d00104a565e451cea9ee8f6b3469d57e42f0796ef95922c866dd0c116a402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c2129055f7442ee5d81e212b8fe0ad7f7766ce50bb85808da00b9acf3187f8e 0.600000000000 1437640 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 977647, "vin": [ { "gen": { "height": 977637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c2129055f7442ee5d81e212b8fe0ad7f7766ce50bb85808da00b9acf3187f8e" } } ], "extra": [ 1, 243, 227, 125, 0, 16, 74, 86, 94, 69, 28, 234, 158, 232, 246, 179, 70, 157, 87, 228, 47, 7, 150, 239, 149, 146, 44, 134, 109, 208, 193, 22, 164, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8