Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0b7e500c8230263b4a63a9ea1ba3dc4ed1086c64f3469a6432b2d8c3e80b9b6

Tx prefix hash: da6924629137ab297f2d0ee2c78dacf47ad771c75a37a4938afc4dc4af3501c0
Tx public key: c049e4977167187edb34ee0fd6a5422b9eee81970081413070f8fd13132c3bb9
Timestamp: 1722702554 Timestamp [UCT]: 2024-08-03 16:29:14 Age [y:d:h:m:s]: 00:257:18:11:33
Block: 1079957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184137 RingCT/type: yes/0
Extra: 01c049e4977167187edb34ee0fd6a5422b9eee81970081413070f8fd13132c3bb902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c4ddbcf45e81fe88458a82f525b820967d2bd1b1bc4553d9d15f121a631fbc 0.600000000000 1553130 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": 1079967, "vin": [ { "gen": { "height": 1079957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c4ddbcf45e81fe88458a82f525b820967d2bd1b1bc4553d9d15f121a631fbc" } } ], "extra": [ 1, 192, 73, 228, 151, 113, 103, 24, 126, 219, 52, 238, 15, 214, 165, 66, 43, 158, 238, 129, 151, 0, 129, 65, 48, 112, 248, 253, 19, 19, 44, 59, 185, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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