Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62607c15a124ef34498f8f610418b2d7cd6dc57c5dce6c2dbac0b3a95e21a291

Tx prefix hash: 90442973edc1ffa2fd1c49aabe9dbc53583f49c7e0561ecfbdcec03cab80ba2f
Tx public key: 2c167e4caea9d8706e4caa0e3668a415045d9e26a04b13ebe1bd8a38ae56fcdb
Timestamp: 1712718881 Timestamp [UCT]: 2024-04-10 03:14:41 Age [y:d:h:m:s]: 01:063:10:53:44
Block: 997170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306328 RingCT/type: yes/0
Extra: 012c167e4caea9d8706e4caa0e3668a415045d9e26a04b13ebe1bd8a38ae56fcdb021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfef9d2e2d3171f7f04080d066b76ff1b78ea7e8b93e416bde17e7247827b43a 0.600000000000 1457600 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": 997180, "vin": [ { "gen": { "height": 997170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfef9d2e2d3171f7f04080d066b76ff1b78ea7e8b93e416bde17e7247827b43a" } } ], "extra": [ 1, 44, 22, 126, 76, 174, 169, 216, 112, 110, 76, 170, 14, 54, 104, 164, 21, 4, 93, 158, 38, 160, 75, 19, 235, 225, 189, 138, 56, 174, 86, 252, 219, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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