Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3a342f3cd4fc59d350a91735b22319d307268d354e044673f5734797927add4

Tx prefix hash: f5ab5ada6d3fae3fdb0ed4125827909c0133b08f5e9b789a7374c0743787efb5
Tx public key: c0da3f9becd6c0628cd5c4f13279adc0eab91651dd9d831c6a211bd20ee207ea
Timestamp: 1712324519 Timestamp [UCT]: 2024-04-05 13:41:59 Age [y:d:h:m:s]: 01:028:01:25:05
Block: 993893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281048 RingCT/type: yes/0
Extra: 01c0da3f9becd6c0628cd5c4f13279adc0eab91651dd9d831c6a211bd20ee207ea02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcdd3c7c798a72ea4da672c5264442e9f68f4554e0f365507042db459cebfa17 0.600000000000 1454289 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": 993903, "vin": [ { "gen": { "height": 993893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcdd3c7c798a72ea4da672c5264442e9f68f4554e0f365507042db459cebfa17" } } ], "extra": [ 1, 192, 218, 63, 155, 236, 214, 192, 98, 140, 213, 196, 241, 50, 121, 173, 192, 234, 185, 22, 81, 221, 157, 131, 28, 106, 33, 27, 210, 14, 226, 7, 234, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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