Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b969153b48a07cf14041ac01cf901a800b71b5cbee18cefd5836fafc721fc35d

Tx prefix hash: 378103844c104c0965ad861aa29a4751ef4c155af66180d235895d444038cdb0
Tx public key: 570a1b4ea5be737db2604df6d9c72ee33daffde7bf1c74c7ff28c7ea54301aa8
Timestamp: 1675048614 Timestamp [UCT]: 2023-01-30 03:16:54 Age [y:d:h:m:s]: 01:348:02:05:31
Block: 685785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509737 RingCT/type: yes/0
Extra: 01570a1b4ea5be737db2604df6d9c72ee33daffde7bf1c74c7ff28c7ea54301aa8021100000006835e4d22000000000000000000

1 output(s) for total of 3.278759381000 dcy

stealth address amount amount idx
00: 3c62fae6d08c37fbdd1458363018d9aee3e0948af510a6f1f08fd942709ac3be 3.278759381000 1128170 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": 685795, "vin": [ { "gen": { "height": 685785 } } ], "vout": [ { "amount": 3278759381, "target": { "key": "3c62fae6d08c37fbdd1458363018d9aee3e0948af510a6f1f08fd942709ac3be" } } ], "extra": [ 1, 87, 10, 27, 78, 165, 190, 115, 125, 178, 96, 77, 246, 217, 199, 46, 227, 61, 175, 253, 231, 191, 28, 116, 199, 255, 40, 199, 234, 84, 48, 26, 168, 2, 17, 0, 0, 0, 6, 131, 94, 77, 34, 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