Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0841699398d545ec33f797728cef213db59d2f5752205abd59b6b9dd8dabf79c

Tx prefix hash: 86aa00fe07f65b9f81e4beaf23f8a22c11608e18948e900749f9c9161e5de954
Tx public key: 0b4ab738c78a5086e6389c5befc2d9ebf48cbee01fda1dcbd6cd4a897cd6da66
Timestamp: 1727780384 Timestamp [UCT]: 2024-10-01 10:59:44 Age [y:d:h:m:s]: 00:112:17:31:48
Block: 1122061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80553 RingCT/type: yes/0
Extra: 010b4ab738c78a5086e6389c5befc2d9ebf48cbee01fda1dcbd6cd4a897cd6da6602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e60f989d5f00518e272d92a41a87643cf6fa65aa24c3d5372ec08d366b9e479d 0.600000000000 1604432 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": 1122071, "vin": [ { "gen": { "height": 1122061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e60f989d5f00518e272d92a41a87643cf6fa65aa24c3d5372ec08d366b9e479d" } } ], "extra": [ 1, 11, 74, 183, 56, 199, 138, 80, 134, 230, 56, 156, 91, 239, 194, 217, 235, 244, 140, 190, 224, 31, 218, 29, 203, 214, 205, 74, 137, 124, 214, 218, 102, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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