Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e784009d146245114b58ccf6bbeca316d46caf9ac458d451d7a1a9b5f668c47

Tx prefix hash: 587d29475c7734cce3aaf1497c584f74257a4dfafc3f033e8012d61a43514250
Tx public key: 9755db483737180b1bf28019e1a94a3df6c87b97260c6e2309a92147d37b181f
Timestamp: 1704758317 Timestamp [UCT]: 2024-01-08 23:58:37 Age [y:d:h:m:s]: 01:092:12:44:34
Block: 931175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327247 RingCT/type: yes/0
Extra: 019755db483737180b1bf28019e1a94a3df6c87b97260c6e2309a92147d37b181f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3790e2fa5c45186fef0d2c747a4efd1e33d952b9310494d2194e33d6385422c 0.600000000000 1389069 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": 931185, "vin": [ { "gen": { "height": 931175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3790e2fa5c45186fef0d2c747a4efd1e33d952b9310494d2194e33d6385422c" } } ], "extra": [ 1, 151, 85, 219, 72, 55, 55, 24, 11, 27, 242, 128, 25, 225, 169, 74, 61, 246, 200, 123, 151, 38, 12, 110, 35, 9, 169, 33, 71, 211, 123, 24, 31, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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