Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d58bf3e617d60b0418ba177357a67a7abef97712ee383b7c598e87d5b0536ff

Tx prefix hash: 109750d89a7c4818d7ed980dc1a47405ecb15b7ec874fc7f8878028bd1036865
Tx public key: 6e11953320309ed677ad93f6e7d3c4e9b599ef03a2ab6e998e951c9ebd7d20c8
Timestamp: 1727781532 Timestamp [UCT]: 2024-10-01 11:18:52 Age [y:d:h:m:s]: 00:208:01:58:08
Block: 1122072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148535 RingCT/type: yes/0
Extra: 016e11953320309ed677ad93f6e7d3c4e9b599ef03a2ab6e998e951c9ebd7d20c802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a36fd8580f8f6bc30efae2ea18175e6a541a339159c42db0fed1ef5429862974 0.600000000000 1604445 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": 1122082, "vin": [ { "gen": { "height": 1122072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a36fd8580f8f6bc30efae2ea18175e6a541a339159c42db0fed1ef5429862974" } } ], "extra": [ 1, 110, 17, 149, 51, 32, 48, 158, 214, 119, 173, 147, 246, 231, 211, 196, 233, 181, 153, 239, 3, 162, 171, 110, 153, 142, 149, 28, 158, 189, 125, 32, 200, 2, 17, 0, 0, 0, 6, 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