Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3e229a0098840dd7c0fc0d9e9e7a41de80364909d573268aa6de46ac893157e

Tx prefix hash: 476ea26236dee864ce047a15d7e68657dd9b82b900576547abc17e498c16995f
Tx public key: f0c349d27153029e574d4df2eaaeffb9de97ed11e5e689150209bb2fd9ac327d
Timestamp: 1756176323 Timestamp [UCT]: 2025-08-26 02:45:23 Age [y:d:h:m:s]: 00:134:13:18:57
Block: 1354546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96177 RingCT/type: yes/0
Extra: 01f0c349d27153029e574d4df2eaaeffb9de97ed11e5e689150209bb2fd9ac327d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d226c8b5067d29d895e32b236decc5acdbd530546ac2d796c351f547e55ba11 0.600000000000 1842535 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": 1354556, "vin": [ { "gen": { "height": 1354546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d226c8b5067d29d895e32b236decc5acdbd530546ac2d796c351f547e55ba11" } } ], "extra": [ 1, 240, 195, 73, 210, 113, 83, 2, 158, 87, 77, 77, 242, 234, 174, 255, 185, 222, 151, 237, 17, 229, 230, 137, 21, 2, 9, 187, 47, 217, 172, 50, 125, 2, 17, 0, 0, 0, 3, 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