Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b1bf2bb8320f7387c395fcb40bebbd91ca0d10b451a4ecded9e6d509f7f5be0

Tx prefix hash: 35b2653bf9c167a35f7070f40afb4425a4da118a89c4927c8909b6a7c46db4e3
Tx public key: d7ecc14b07a88c7c058c415aefeefc5f77c5213446f556390709a20ce59fc0f0
Timestamp: 1748289960 Timestamp [UCT]: 2025-05-26 20:06:00 Age [y:d:h:m:s]: 00:179:03:16:57
Block: 1291556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125717 RingCT/type: yes/0
Extra: 01d7ecc14b07a88c7c058c415aefeefc5f77c5213446f556390709a20ce59fc0f002110000000186ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afee89da8004ffc616210bb90739f0642bb19f4d350aa629eb632861567d26e8 0.600000000000 1779027 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": 1291566, "vin": [ { "gen": { "height": 1291556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afee89da8004ffc616210bb90739f0642bb19f4d350aa629eb632861567d26e8" } } ], "extra": [ 1, 215, 236, 193, 75, 7, 168, 140, 124, 5, 140, 65, 90, 239, 238, 252, 95, 119, 197, 33, 52, 70, 245, 86, 57, 7, 9, 162, 12, 229, 159, 192, 240, 2, 17, 0, 0, 0, 1, 134, 174, 47, 13, 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