Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4000b0288606068541717aa59cb92b54ffb34040e322c96f6f66b14dec700c6

Tx prefix hash: bf463231e0c946f27c05c9f43cdc489f14d9521bf9a303812d8b2676da94c708
Tx public key: 493e32c828939f1ce9c463d1622f5bcc817d84b6a0a1253d59cc435bc977b8a7
Timestamp: 1726172163 Timestamp [UCT]: 2024-09-12 20:16:03 Age [y:d:h:m:s]: 00:232:00:19:15
Block: 1108721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165665 RingCT/type: yes/0
Extra: 01493e32c828939f1ce9c463d1622f5bcc817d84b6a0a1253d59cc435bc977b8a702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dbf8793bae39501b9157afd6a7030f4238f9a5d0d1a0a607b2cee119be808f0 0.600000000000 1586718 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": 1108731, "vin": [ { "gen": { "height": 1108721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dbf8793bae39501b9157afd6a7030f4238f9a5d0d1a0a607b2cee119be808f0" } } ], "extra": [ 1, 73, 62, 50, 200, 40, 147, 159, 28, 233, 196, 99, 209, 98, 47, 91, 204, 129, 125, 132, 182, 160, 161, 37, 61, 89, 204, 67, 91, 201, 119, 184, 167, 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