Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8238ebae0b1feac0e4a0fed49da9ea1bd47118b5fdbeff524302fecdf796e81

Tx prefix hash: df092a5b3509081cc950fcc31c11661f4eb7d177750e62fd848ea42ee8e0d57e
Tx public key: c99f55ed45d71fe05b7befee7638ac051dc651b14df8e1daed46c8fa1f014d39
Timestamp: 1730442451 Timestamp [UCT]: 2024-11-01 06:27:31 Age [y:d:h:m:s]: 00:023:00:31:46
Block: 1144044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16474 RingCT/type: yes/0
Extra: 01c99f55ed45d71fe05b7befee7638ac051dc651b14df8e1daed46c8fa1f014d390211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c412c4b93b5267a9bcca653cd15d623238eafa2caa708dfb42b04a8436ba03b0 0.600000000000 1628119 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": 1144054, "vin": [ { "gen": { "height": 1144044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c412c4b93b5267a9bcca653cd15d623238eafa2caa708dfb42b04a8436ba03b0" } } ], "extra": [ 1, 201, 159, 85, 237, 69, 215, 31, 224, 91, 123, 239, 238, 118, 56, 172, 5, 29, 198, 81, 177, 77, 248, 225, 218, 237, 70, 200, 250, 31, 1, 77, 57, 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