Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 661a712e5718af42b5efdb6f363e38a1dba982f4ab0f489e8cb49e153872fcb4

Tx prefix hash: b41700d5a927c9b23a22fbcf30278bd7f29a3bf7347f518a3ad733141fb9c6a0
Tx public key: c2eccc9ef9cf17f6958dae9fcd794c46622b9ea55b9b69aa48acffefa362c990
Timestamp: 1736427242 Timestamp [UCT]: 2025-01-09 12:54:02 Age [y:d:h:m:s]: 00:314:14:12:37
Block: 1193609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222347 RingCT/type: yes/0
Extra: 01c2eccc9ef9cf17f6958dae9fcd794c46622b9ea55b9b69aa48acffefa362c9900211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a28dae004f7dc84262e1bf1e78ca1ad8ee5805a43a821c5fec4747a9744ad257 0.600000000000 1680172 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": 1193619, "vin": [ { "gen": { "height": 1193609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a28dae004f7dc84262e1bf1e78ca1ad8ee5805a43a821c5fec4747a9744ad257" } } ], "extra": [ 1, 194, 236, 204, 158, 249, 207, 23, 246, 149, 141, 174, 159, 205, 121, 76, 70, 98, 43, 158, 165, 91, 155, 105, 170, 72, 172, 255, 239, 163, 98, 201, 144, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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