Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4ce6d50d7905c08e3a00506a82495613fae1e736df5d69f541bee83c9448c9c

Tx prefix hash: 1f23184ffd4d96ac3de333a24edeea0e571f915296de591b665beab31f5c5a5a
Tx public key: 4f0b4828b5c4938d823a0e0eecb9df125343e709aa2c34283cb484cdde313c89
Timestamp: 1726395491 Timestamp [UCT]: 2024-09-15 10:18:11 Age [y:d:h:m:s]: 00:117:02:56:53
Block: 1110577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83753 RingCT/type: yes/0
Extra: 014f0b4828b5c4938d823a0e0eecb9df125343e709aa2c34283cb484cdde313c89021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3601d9c3c199d2fb30b0c72a331c2edec9414784466988660cb4a84f98afb5e 0.600000000000 1589232 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": 1110587, "vin": [ { "gen": { "height": 1110577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3601d9c3c199d2fb30b0c72a331c2edec9414784466988660cb4a84f98afb5e" } } ], "extra": [ 1, 79, 11, 72, 40, 181, 196, 147, 141, 130, 58, 14, 14, 236, 185, 223, 18, 83, 67, 231, 9, 170, 44, 52, 40, 60, 180, 132, 205, 222, 49, 60, 137, 2, 17, 0, 0, 0, 3, 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