Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b937a8441e6eb320062a2664a9d45d593aa9354b4e80a12775a9a6d13127a385

Tx prefix hash: 36543a207c6c1dfe319eb86ca42c88ff06ff5aacef5158cfbdea4246979d56d5
Tx public key: 1e46f94399f48a01d7eff5cc9f4638143fb8db8269471a120aa87c3cb3ce86b7
Timestamp: 1726363273 Timestamp [UCT]: 2024-09-15 01:21:13 Age [y:d:h:m:s]: 00:161:02:16:07
Block: 1110303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114931 RingCT/type: yes/0
Extra: 011e46f94399f48a01d7eff5cc9f4638143fb8db8269471a120aa87c3cb3ce86b702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03db6c3790f2b3c283745bf23a31680b03c6a184229e197186a21d9562f2cf61 0.600000000000 1588860 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": 1110313, "vin": [ { "gen": { "height": 1110303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03db6c3790f2b3c283745bf23a31680b03c6a184229e197186a21d9562f2cf61" } } ], "extra": [ 1, 30, 70, 249, 67, 153, 244, 138, 1, 215, 239, 245, 204, 159, 70, 56, 20, 63, 184, 219, 130, 105, 71, 26, 18, 10, 168, 124, 60, 179, 206, 134, 183, 2, 17, 0, 0, 0, 5, 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