Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3d4aa8ee3ef53f0b52917b8cd0a2cc59bc9244929ffd9ac15641f57f5e15f68

Tx prefix hash: 0945844c1603300fe85f666fbd6e3dac10aeee5fd5ff18eb047653a697ce3299
Tx public key: dc19e6f9a641b43987432a7b26c5411cddd60d287ba04ff89e8860a4551d781a
Timestamp: 1714365422 Timestamp [UCT]: 2024-04-29 04:37:02 Age [y:d:h:m:s]: 00:200:07:51:10
Block: 1010838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143400 RingCT/type: yes/0
Extra: 01dc19e6f9a641b43987432a7b26c5411cddd60d287ba04ff89e8860a4551d781a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11acd5a24d2be1f2d8b1b8440e1dcf9faddd37fe3792a1af535fa1c49d69711d 0.600000000000 1472900 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": 1010848, "vin": [ { "gen": { "height": 1010838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11acd5a24d2be1f2d8b1b8440e1dcf9faddd37fe3792a1af535fa1c49d69711d" } } ], "extra": [ 1, 220, 25, 230, 249, 166, 65, 180, 57, 135, 67, 42, 123, 38, 197, 65, 28, 221, 214, 13, 40, 123, 160, 79, 248, 158, 136, 96, 164, 85, 29, 120, 26, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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