Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fae92e00ab1cf9761081f4eeb41e7fa91db95c3ca1f4e13f1db79e162b647c6

Tx prefix hash: 16c867dc8f2809695cae16f583fcb0314edb5c46a4f0a416c8a2732b19b8e3d7
Tx public key: 4f94adf887b6d90291ec100aa20e6c0f86fec95ee5a28c9066052cedeeeb448e
Timestamp: 1704669760 Timestamp [UCT]: 2024-01-07 23:22:40 Age [y:d:h:m:s]: 01:022:00:39:15
Block: 930442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276829 RingCT/type: yes/0
Extra: 014f94adf887b6d90291ec100aa20e6c0f86fec95ee5a28c9066052cedeeeb448e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 532ed679258285cbf22ba3c5147e841e3253f102292680dfbaf5fa2b51deabd1 0.600000000000 1388324 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": 930452, "vin": [ { "gen": { "height": 930442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "532ed679258285cbf22ba3c5147e841e3253f102292680dfbaf5fa2b51deabd1" } } ], "extra": [ 1, 79, 148, 173, 248, 135, 182, 217, 2, 145, 236, 16, 10, 162, 14, 108, 15, 134, 254, 201, 94, 229, 162, 140, 144, 102, 5, 44, 237, 238, 235, 68, 142, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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