Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3c6f8e57c22c6f85184e62e71029a7225edcbf12057b25b042bce64be50c58b

Tx prefix hash: af4c4a9e3dd79c44b01314365593fb923ec8e4315ec12d0c6afc4ae6468da104
Tx public key: 54312f78aa41203ad3dc0a020c078e189d0770529b6a6c38d83eb73eb6359fd1
Timestamp: 1761725708 Timestamp [UCT]: 2025-10-29 08:15:08 Age [y:d:h:m:s]: 00:021:20:34:02
Block: 1400374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15638 RingCT/type: yes/0
Extra: 0154312f78aa41203ad3dc0a020c078e189d0770529b6a6c38d83eb73eb6359fd1021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df8656380f5fa002367aad5c304a3e06f155262b75e961d1060b3f30ad7de0f 0.600000000000 1888681 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": 1400384, "vin": [ { "gen": { "height": 1400374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df8656380f5fa002367aad5c304a3e06f155262b75e961d1060b3f30ad7de0f" } } ], "extra": [ 1, 84, 49, 47, 120, 170, 65, 32, 58, 211, 220, 10, 2, 12, 7, 142, 24, 157, 7, 112, 82, 155, 106, 108, 56, 216, 62, 183, 62, 182, 53, 159, 209, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 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