Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9973e2a8486677f0d97e2842c5eb2a80adf7be57c993bc7cb8d1c96421a0dead

Tx prefix hash: 2508173ab676186fbf6a0098054f5d6ce4c997738043b3cdfc523912a5e7f360
Tx public key: c6f133a56416419df1c07948faac067cb86c67e4e4de38f985e7a1aaa6e26730
Timestamp: 1709650273 Timestamp [UCT]: 2024-03-05 14:51:13 Age [y:d:h:m:s]: 01:109:08:01:02
Block: 971759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338979 RingCT/type: yes/0
Extra: 01c6f133a56416419df1c07948faac067cb86c67e4e4de38f985e7a1aaa6e267300211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04663b6683584bb0fd01d43644e218108360417ac0c676519f4825ddff89a06 0.600000000000 1431660 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": 971769, "vin": [ { "gen": { "height": 971759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04663b6683584bb0fd01d43644e218108360417ac0c676519f4825ddff89a06" } } ], "extra": [ 1, 198, 241, 51, 165, 100, 22, 65, 157, 241, 192, 121, 72, 250, 172, 6, 124, 184, 108, 103, 228, 228, 222, 56, 249, 133, 231, 161, 170, 166, 226, 103, 48, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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