Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3462a1b7f6bcf62b2607521554117eb7c6237702015d68df1c4b7faa75fcd3cb

Tx prefix hash: 038b758675443a9d6a77585df8bbe7803c9fabe3fced42c6f570d203931333d6
Tx public key: 2f45c1a7f72651d3cca95c59c89a032b2a9fba8aafc62eca571e7d698b779031
Timestamp: 1709183108 Timestamp [UCT]: 2024-02-29 05:05:08 Age [y:d:h:m:s]: 01:026:06:15:28
Block: 967879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279755 RingCT/type: yes/0
Extra: 012f45c1a7f72651d3cca95c59c89a032b2a9fba8aafc62eca571e7d698b77903102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0ce2764f630c77cb5d7fcdd603743ec0ab756fe38a5d2adeafec55ad8221df6 0.600000000000 1427670 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": 967889, "vin": [ { "gen": { "height": 967879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ce2764f630c77cb5d7fcdd603743ec0ab756fe38a5d2adeafec55ad8221df6" } } ], "extra": [ 1, 47, 69, 193, 167, 247, 38, 81, 211, 204, 169, 92, 89, 200, 154, 3, 43, 42, 159, 186, 138, 175, 198, 46, 202, 87, 30, 125, 105, 139, 119, 144, 49, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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