Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b86aa41ea02b15a11dfe1b32677fab40cfdd2214bc14301acbdd1bc942d8d8c

Tx prefix hash: 445ef202c0e074eafbb01ea49bbdc151a6fd9b509e41e8344dacb5be4e42e3d0
Tx public key: 1ede7dc426699e568fe9252a3a084302a2c9d21bfa395b07e20bedc378030386
Timestamp: 1724236891 Timestamp [UCT]: 2024-08-21 10:41:31 Age [y:d:h:m:s]: 01:077:14:03:20
Block: 1092696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313879 RingCT/type: yes/0
Extra: 011ede7dc426699e568fe9252a3a084302a2c9d21bfa395b07e20bedc378030386021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 755fbc048ab444b7eb4839fe20b2fbcf9316e5e5f0c3e3da8fa26ad8f4a75dee 0.600000000000 1567493 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": 1092706, "vin": [ { "gen": { "height": 1092696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "755fbc048ab444b7eb4839fe20b2fbcf9316e5e5f0c3e3da8fa26ad8f4a75dee" } } ], "extra": [ 1, 30, 222, 125, 196, 38, 105, 158, 86, 143, 233, 37, 42, 58, 8, 67, 2, 162, 201, 210, 27, 250, 57, 91, 7, 226, 11, 237, 195, 120, 3, 3, 134, 2, 17, 0, 0, 0, 7, 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