Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72fc2c6bcab4c9c5190327b65a01a3aa4fb3ce60e21d14826d4c28388ac19d56

Tx prefix hash: 884ed79a9aeb8ab2b0b9b428d8fc082788ca544be7bdf4f42c9f68cf02a61f88
Tx public key: b523389f2cb3788ec14111e156b43753227f509fb3742419f30967281fa5871e
Timestamp: 1751398068 Timestamp [UCT]: 2025-07-01 19:27:48 Age [y:d:h:m:s]: 00:135:15:18:34
Block: 1316737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95156 RingCT/type: yes/0
Extra: 01b523389f2cb3788ec14111e156b43753227f509fb3742419f30967281fa5871e021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fa97caea66f4a1b4c806ac6b8940e6b141e0a523d72bdf9893e25b8c67e203d 0.600000000000 1804400 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": 1316747, "vin": [ { "gen": { "height": 1316737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa97caea66f4a1b4c806ac6b8940e6b141e0a523d72bdf9893e25b8c67e203d" } } ], "extra": [ 1, 181, 35, 56, 159, 44, 179, 120, 142, 193, 65, 17, 225, 86, 180, 55, 83, 34, 127, 80, 159, 179, 116, 36, 25, 243, 9, 103, 40, 31, 165, 135, 30, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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