Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9407bfaaa5114fe24f19edf42ea55cd4b9c2e445e5ad1f6a6edd73b11bae73cf

Tx prefix hash: 4deee7cf12db0f8314b895455d1b43f964dc24ab2a5387c3e946a45aca6e3abc
Tx public key: 4bad87e0d41801dc5cad4cc7e0ea3a3d8a12bac75ee1049d4d0af69cbcc9284b
Timestamp: 1724358601 Timestamp [UCT]: 2024-08-22 20:30:01 Age [y:d:h:m:s]: 01:079:03:00:58
Block: 1093701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314994 RingCT/type: yes/0
Extra: 014bad87e0d41801dc5cad4cc7e0ea3a3d8a12bac75ee1049d4d0af69cbcc9284b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71c244d4ac818dc8079b9aea81c57cb9417c96d544a334d3af1453b5df4646c 0.600000000000 1568696 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": 1093711, "vin": [ { "gen": { "height": 1093701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71c244d4ac818dc8079b9aea81c57cb9417c96d544a334d3af1453b5df4646c" } } ], "extra": [ 1, 75, 173, 135, 224, 212, 24, 1, 220, 92, 173, 76, 199, 224, 234, 58, 61, 138, 18, 186, 199, 94, 225, 4, 157, 77, 10, 246, 156, 188, 201, 40, 75, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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