Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6233645aa7c50bfdae753e0d2623f17564e79a48180167f8c3dfc4e79e3147f8

Tx prefix hash: c176f64b56cad5acb7946f3b22bd87798b733f0fa9bdd7a451a3b77abc4a1587
Tx public key: e9a7bd62659051d4fb11751120de1b7085c0f722ad5ff1c4e56249d021666415
Timestamp: 1760587550 Timestamp [UCT]: 2025-10-16 04:05:50 Age [y:d:h:m:s]: 00:022:23:29:36
Block: 1390927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16455 RingCT/type: yes/0
Extra: 01e9a7bd62659051d4fb11751120de1b7085c0f722ad5ff1c4e56249d0216664150211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3d2ceb8f31b54212f4d9d56799a9ce17dd8c3e5e33703c5ce2c27960808eefa 0.600000000000 1879174 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": 1390937, "vin": [ { "gen": { "height": 1390927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3d2ceb8f31b54212f4d9d56799a9ce17dd8c3e5e33703c5ce2c27960808eefa" } } ], "extra": [ 1, 233, 167, 189, 98, 101, 144, 81, 212, 251, 17, 117, 17, 32, 222, 27, 112, 133, 192, 247, 34, 173, 95, 241, 196, 229, 98, 73, 208, 33, 102, 100, 21, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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