Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70a0fa371f3dcacf9f7a3892ed273bebb4dbee6aa930590e985d0d1769473e2d

Tx prefix hash: 171949fe1e9f5f7b7be3b2fbb3a1845a0162b64e1537801ec600021c2591ad6e
Tx public key: 9c3b27eca5fbddc712f4ccadba626d4cb24ed36ca70a37796f4ed9fe7b206292
Timestamp: 1720452442 Timestamp [UCT]: 2024-07-08 15:27:22 Age [y:d:h:m:s]: 00:202:14:33:01
Block: 1061317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144721 RingCT/type: yes/0
Extra: 019c3b27eca5fbddc712f4ccadba626d4cb24ed36ca70a37796f4ed9fe7b20629202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33b22b7916d4a4401bd2f68cd5be0ab122df57c6abfadf011309ecd54655a626 0.600000000000 1531808 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": 1061327, "vin": [ { "gen": { "height": 1061317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33b22b7916d4a4401bd2f68cd5be0ab122df57c6abfadf011309ecd54655a626" } } ], "extra": [ 1, 156, 59, 39, 236, 165, 251, 221, 199, 18, 244, 204, 173, 186, 98, 109, 76, 178, 78, 211, 108, 167, 10, 55, 121, 111, 78, 217, 254, 123, 32, 98, 146, 2, 17, 0, 0, 0, 6, 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