Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54834a6f6480bc71123fc2da4abe3cd0f0f578aa8540dcf31f70f763d6c42c3d

Tx prefix hash: 738edfbb1305b21111a13657a816bbca123cf394b77d40367aed16a5b009b3c3
Tx public key: 5c11fba3c931274e3210287aae7d75da4200a9fe9af49b368e0df277038a5271
Timestamp: 1749155227 Timestamp [UCT]: 2025-06-05 20:27:07 Age [y:d:h:m:s]: 00:161:01:40:40
Block: 1298712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112801 RingCT/type: yes/0
Extra: 015c11fba3c931274e3210287aae7d75da4200a9fe9af49b368e0df277038a5271021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0df6b115bb87e6aed76c2acc9b38cd2c4c2203295999352bf1a7a3f85415dd6a 0.600000000000 1786241 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": 1298722, "vin": [ { "gen": { "height": 1298712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0df6b115bb87e6aed76c2acc9b38cd2c4c2203295999352bf1a7a3f85415dd6a" } } ], "extra": [ 1, 92, 17, 251, 163, 201, 49, 39, 78, 50, 16, 40, 122, 174, 125, 117, 218, 66, 0, 169, 254, 154, 244, 155, 54, 142, 13, 242, 119, 3, 138, 82, 113, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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