Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de5c6fb53eb9e5ccdd4bda7222f6b7872e4c9ab066693660d919b692ad63a1a5

Tx prefix hash: 680fcdf94a740352e370935f6290634a274c32e424fd837f6b53cec2f5b704ee
Tx public key: 1c36bd3f9c98f190c8b7d6606f6c422efc60d7e1b78c51d0f36f50d31e3a2094
Timestamp: 1737288870 Timestamp [UCT]: 2025-01-19 12:14:30 Age [y:d:h:m:s]: 00:305:04:28:14
Block: 1200701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215656 RingCT/type: yes/0
Extra: 011c36bd3f9c98f190c8b7d6606f6c422efc60d7e1b78c51d0f36f50d31e3a2094021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3afcd12b41c942a575151679339dc604c8f7084bb16fbd73f9ffe84df5fd9829 0.600000000000 1687346 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": 1200711, "vin": [ { "gen": { "height": 1200701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3afcd12b41c942a575151679339dc604c8f7084bb16fbd73f9ffe84df5fd9829" } } ], "extra": [ 1, 28, 54, 189, 63, 156, 152, 241, 144, 200, 183, 214, 96, 111, 108, 66, 46, 252, 96, 215, 225, 183, 140, 81, 208, 243, 111, 80, 211, 30, 58, 32, 148, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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