Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833413bb2777fdf41686a3cd9577bdd6f694ec7ffa75b297b08df93e3a9b033f

Tx prefix hash: a775b0ec0ceffbc949665f48e1300da95260e9f43ea7947c0fc0c50e1801028b
Tx public key: 09748d5e5ad6e2abe2afb4b0e2fe421bf3345626257844cf4a815ebf892193ad
Timestamp: 1721322883 Timestamp [UCT]: 2024-07-18 17:14:43 Age [y:d:h:m:s]: 00:268:21:18:43
Block: 1068540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192086 RingCT/type: yes/0
Extra: 0109748d5e5ad6e2abe2afb4b0e2fe421bf3345626257844cf4a815ebf892193ad02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5438f9f235e2a4d1bf2ca7e9e5d4ecdfdefd92c96011a4896787a80bce2bdb6c 0.600000000000 1539619 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": 1068550, "vin": [ { "gen": { "height": 1068540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5438f9f235e2a4d1bf2ca7e9e5d4ecdfdefd92c96011a4896787a80bce2bdb6c" } } ], "extra": [ 1, 9, 116, 141, 94, 90, 214, 226, 171, 226, 175, 180, 176, 226, 254, 66, 27, 243, 52, 86, 38, 37, 120, 68, 207, 74, 129, 94, 191, 137, 33, 147, 173, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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