Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87edd7f298902a50c6bfbceaa443872d65f066359686926cfe70abcc53fd6bf

Tx prefix hash: fa9ef4985216aeddab679013e22999f3be0af00f96556c5f6109698d01daaef2
Tx public key: bd28a8737eb8f3547aadaf57a1b7b1d9d0a566b9f3231addd0537f2af4e0c05e
Timestamp: 1753772248 Timestamp [UCT]: 2025-07-29 06:57:28 Age [y:d:h:m:s]: 00:071:12:47:12
Block: 1335767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49891 RingCT/type: yes/0
Extra: 01bd28a8737eb8f3547aadaf57a1b7b1d9d0a566b9f3231addd0537f2af4e0c05e021100000002db6acbd3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ade2a0c346dfbfe5aedf013d6d1c59b5938f1e732746b22850c986eee2ffc15 0.600000000000 1823568 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": 1335777, "vin": [ { "gen": { "height": 1335767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ade2a0c346dfbfe5aedf013d6d1c59b5938f1e732746b22850c986eee2ffc15" } } ], "extra": [ 1, 189, 40, 168, 115, 126, 184, 243, 84, 122, 173, 175, 87, 161, 183, 177, 217, 208, 165, 102, 185, 243, 35, 26, 221, 208, 83, 127, 42, 244, 224, 192, 94, 2, 17, 0, 0, 0, 2, 219, 106, 203, 211, 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