Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8017c4fc1f0970edbfc7a896d9ccc88e27da0b413916cdcc57a6f06db02bbc5

Tx prefix hash: dd1d8c8607f32cef6af30c8756bddc45d786ce1caf7775cde77a8788480f70d3
Tx public key: 7446726e2d83dba35e08093962749ecbb4fd6d684acab81ebd2e5a9eb6793ea4
Timestamp: 1727195792 Timestamp [UCT]: 2024-09-24 16:36:32 Age [y:d:h:m:s]: 00:060:20:56:30
Block: 1117212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43502 RingCT/type: yes/0
Extra: 017446726e2d83dba35e08093962749ecbb4fd6d684acab81ebd2e5a9eb6793ea4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 249bfb7ac8587d0584e3e294907e9799a3f873ae457721849b95e8c1ff9c5ee7 0.600000000000 1597969 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": 1117222, "vin": [ { "gen": { "height": 1117212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "249bfb7ac8587d0584e3e294907e9799a3f873ae457721849b95e8c1ff9c5ee7" } } ], "extra": [ 1, 116, 70, 114, 110, 45, 131, 219, 163, 94, 8, 9, 57, 98, 116, 158, 203, 180, 253, 109, 104, 74, 202, 184, 30, 189, 46, 90, 158, 182, 121, 62, 164, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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