Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870537567d0670bfe14cf51c41b122f117de90092ec7ae2d79cbd06d262ec682

Tx prefix hash: e17e8b2c09a6bc581ed85c6d6e8519f4a4f389c3dae0d0757cebc1e2d2880bf3
Tx public key: 59d12ef84433aa382b46c6ad09926686a721266abef8a0bfe1deb23f5abeb9c8
Timestamp: 1729221476 Timestamp [UCT]: 2024-10-18 03:17:56 Age [y:d:h:m:s]: 00:179:08:11:32
Block: 1134008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127948 RingCT/type: yes/0
Extra: 0159d12ef84433aa382b46c6ad09926686a721266abef8a0bfe1deb23f5abeb9c80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 6279393e30cc22500212090e48102e1c68232d845f8ccb850b65e1a2aeaa3fc8 0.600010000000 1617241 of 0

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": 1134018, "vin": [ { "gen": { "height": 1134008 } } ], "vout": [ { "amount": 600010000, "target": { "key": "6279393e30cc22500212090e48102e1c68232d845f8ccb850b65e1a2aeaa3fc8" } } ], "extra": [ 1, 89, 209, 46, 248, 68, 51, 170, 56, 43, 70, 198, 173, 9, 146, 102, 134, 167, 33, 38, 106, 190, 248, 160, 191, 225, 222, 178, 63, 90, 190, 185, 200, 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