Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aacf5283edd25ec38b1ac294131f9662be553c962d0f6cdbbcb40d94fef2364

Tx prefix hash: 326e242797b956a49f0cb89b4924be1b99eb604dd66d48cde2f236811060fc63
Tx public key: 90c00f5bf8ff5f61488974fd33de08aebd6707507f01dbdc4e0a73cf9b867f73
Timestamp: 1734927127 Timestamp [UCT]: 2024-12-23 04:12:07 Age [y:d:h:m:s]: 00:099:01:01:27
Block: 1181221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70541 RingCT/type: yes/0
Extra: 0190c00f5bf8ff5f61488974fd33de08aebd6707507f01dbdc4e0a73cf9b867f73021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a8b42639e7a9262bcb959e8e10a9aacd6de36412d95b1e2ff2444132a0429b7 0.600000000000 1667638 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": 1181231, "vin": [ { "gen": { "height": 1181221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a8b42639e7a9262bcb959e8e10a9aacd6de36412d95b1e2ff2444132a0429b7" } } ], "extra": [ 1, 144, 192, 15, 91, 248, 255, 95, 97, 72, 137, 116, 253, 51, 222, 8, 174, 189, 103, 7, 80, 127, 1, 219, 220, 78, 10, 115, 207, 155, 134, 127, 115, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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