Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a06da66d5298dd5981d6c08d9a7eb5de09454bc29cbf0cb5360c991510c82da6

Tx prefix hash: f64e616bbd905a6b45e0c825f7a57ac77baea92a16a7e60b921a5762776a44ce
Tx public key: 5321a01ba5227c223d021ceff457c1a8e9249c247d7af7f7b1854fcbfec82344
Timestamp: 1733012466 Timestamp [UCT]: 2024-12-01 00:21:06 Age [y:d:h:m:s]: 00:028:17:51:25
Block: 1165336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20551 RingCT/type: yes/0
Extra: 015321a01ba5227c223d021ceff457c1a8e9249c247d7af7f7b1854fcbfec823440211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 293ad65618ef51903fdd6317e28ac24ae253e16fad66a13fa0d0b7d2d961a722 0.600000000000 1651011 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": 1165346, "vin": [ { "gen": { "height": 1165336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293ad65618ef51903fdd6317e28ac24ae253e16fad66a13fa0d0b7d2d961a722" } } ], "extra": [ 1, 83, 33, 160, 27, 165, 34, 124, 34, 61, 2, 28, 239, 244, 87, 193, 168, 233, 36, 156, 36, 125, 122, 247, 247, 177, 133, 79, 203, 254, 200, 35, 68, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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