Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fab0da255b5049a47739e4c87a3f7f9417184cd19352ef54c8154e891e7bedf4

Tx prefix hash: f519558437346263cdb7431bb8bff211e23a17ffe040f21a84397a3b715cf7e6
Tx public key: 500d5c1266beb8b3442bf96dad1a074b6f9adb3bb338b26b83213aec3e9180fe
Timestamp: 1725772399 Timestamp [UCT]: 2024-09-08 05:13:19 Age [y:d:h:m:s]: 00:249:19:19:37
Block: 1105414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178397 RingCT/type: yes/0
Extra: 01500d5c1266beb8b3442bf96dad1a074b6f9adb3bb338b26b83213aec3e9180fe021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae73eb9783aabe527d4c4ca20de82f389332aafd1fe3dcf6619b0a5d64d8b0a7 0.600000000000 1582757 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": 1105424, "vin": [ { "gen": { "height": 1105414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae73eb9783aabe527d4c4ca20de82f389332aafd1fe3dcf6619b0a5d64d8b0a7" } } ], "extra": [ 1, 80, 13, 92, 18, 102, 190, 184, 179, 68, 43, 249, 109, 173, 26, 7, 75, 111, 154, 219, 59, 179, 56, 178, 107, 131, 33, 58, 236, 62, 145, 128, 254, 2, 17, 0, 0, 0, 1, 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