Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1584f19512ab5c47ef4aa481d4310a8045b7b18d6da99509c15e539b927c50a3

Tx prefix hash: 4477e3e407929b4bc17eb63d7b732dcf29a93717a24a6d49b2b9a8a205e349bc
Tx public key: 8acb89b939cf68f75b11f0beec4e63627801d2611cad3f0f502a8fdd9c658494
Timestamp: 1742505938 Timestamp [UCT]: 2025-03-20 21:25:38 Age [y:d:h:m:s]: 00:093:01:06:13
Block: 1243680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66374 RingCT/type: yes/0
Extra: 018acb89b939cf68f75b11f0beec4e63627801d2611cad3f0f502a8fdd9c658494021100000003bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e16abb8e1f0d2b703f6c69e0baf7bd3f218c3d841902828f486b8dda29f885 0.600000000000 1730667 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": 1243690, "vin": [ { "gen": { "height": 1243680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e16abb8e1f0d2b703f6c69e0baf7bd3f218c3d841902828f486b8dda29f885" } } ], "extra": [ 1, 138, 203, 137, 185, 57, 207, 104, 247, 91, 17, 240, 190, 236, 78, 99, 98, 120, 1, 210, 97, 28, 173, 63, 15, 80, 42, 143, 221, 156, 101, 132, 148, 2, 17, 0, 0, 0, 3, 191, 167, 118, 35, 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