Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d10d3f485757c22c31c555d05a06683ad600e974c66ae42d2c2167effd72fbf

Tx prefix hash: 05e0abfa0a2d1183ab791b3648714a67ce287c3e9c30efb200c96b2d7656ec43
Tx public key: 8d711fd8da552c0b07f673f195367190b4005f3c8628f194d1bb3cc1e9063df8
Timestamp: 1728002395 Timestamp [UCT]: 2024-10-04 00:39:55 Age [y:d:h:m:s]: 01:035:14:12:22
Block: 1123908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283812 RingCT/type: yes/0
Extra: 018d711fd8da552c0b07f673f195367190b4005f3c8628f194d1bb3cc1e9063df802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d16dde4e1a54d548767c4067a3aa43913c49c4d1ac46335cc4c6d1fdae25344f 0.600000000000 1606457 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": 1123918, "vin": [ { "gen": { "height": 1123908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d16dde4e1a54d548767c4067a3aa43913c49c4d1ac46335cc4c6d1fdae25344f" } } ], "extra": [ 1, 141, 113, 31, 216, 218, 85, 44, 11, 7, 246, 115, 241, 149, 54, 113, 144, 180, 0, 95, 60, 134, 40, 241, 148, 209, 187, 60, 193, 233, 6, 61, 248, 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