Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3fd1277129922f6316397203baee0667b77f5e1b3d4b78b95546e2b90907d94

Tx prefix hash: dcb9ad820c5f6e03d1909794ed08c7cf705a29816e6fee96cca0c7a77802fe78
Tx public key: 0163907f5e1d0c4fb6934e5a4163cf5e20195a672e926d13c75a63e56d9b1dbf
Timestamp: 1729487165 Timestamp [UCT]: 2024-10-21 05:06:05 Age [y:d:h:m:s]: 00:093:15:41:10
Block: 1136171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66926 RingCT/type: yes/0
Extra: 010163907f5e1d0c4fb6934e5a4163cf5e20195a672e926d13c75a63e56d9b1dbf021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c28baaaf1a9659a6c7c2013d85a4f2de690dbf3e3a5a0498d6f2ce32d6bae86 0.600000000000 1619514 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": 1136181, "vin": [ { "gen": { "height": 1136171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c28baaaf1a9659a6c7c2013d85a4f2de690dbf3e3a5a0498d6f2ce32d6bae86" } } ], "extra": [ 1, 1, 99, 144, 127, 94, 29, 12, 79, 182, 147, 78, 90, 65, 99, 207, 94, 32, 25, 90, 103, 46, 146, 109, 19, 199, 90, 99, 229, 109, 155, 29, 191, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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