Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd58e436a17ce47e603225641e3369dc3cc2df1e5bc0f3a2e0e8f9ee594a8dc9

Tx prefix hash: a4720a257d537c123fa00703f2b22b21a988162fbec8a7b7f4929430dfee7b12
Tx public key: dc66037291dacbcfd6c44ad0f64fa40eea0c22f1e4da3cf8a73abac3c9511424
Timestamp: 1696556332 Timestamp [UCT]: 2023-10-06 01:38:52 Age [y:d:h:m:s]: 01:187:15:19:52
Block: 863391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395153 RingCT/type: yes/0
Extra: 01dc66037291dacbcfd6c44ad0f64fa40eea0c22f1e4da3cf8a73abac3c9511424021100000003faf35c9c000000000000000000

1 output(s) for total of 0.845721251000 dcy

stealth address amount amount idx
00: b31931bb5d8d1c64346a0c186ed781908b790a05c219245e0dbf6c0386de79d0 0.845721251000 1317843 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": 863401, "vin": [ { "gen": { "height": 863391 } } ], "vout": [ { "amount": 845721251, "target": { "key": "b31931bb5d8d1c64346a0c186ed781908b790a05c219245e0dbf6c0386de79d0" } } ], "extra": [ 1, 220, 102, 3, 114, 145, 218, 203, 207, 214, 196, 74, 208, 246, 79, 164, 14, 234, 12, 34, 241, 228, 218, 60, 248, 167, 58, 186, 195, 201, 81, 20, 36, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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