Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8875553bb044be43bd3c3e0ca426e9560953587aded89110a698e50b48b6072

Tx prefix hash: 727afa70b13c1c132918a35209123b6085b3bfe94925d8c1488df7ff0888e3b7
Tx public key: d4e5de7d0b9bb6e2bc83a0c680eee57c9674a757f7d8b9faa54bd4d229b440e3
Timestamp: 1746288357 Timestamp [UCT]: 2025-05-03 16:05:57 Age [y:d:h:m:s]: 00:201:22:57:29
Block: 1274977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142043 RingCT/type: yes/0
Extra: 01d4e5de7d0b9bb6e2bc83a0c680eee57c9674a757f7d8b9faa54bd4d229b440e302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6a2de84fdef24cf83b01d0276f934e46eeb9d3473909f24a9ee63fb8d247501 0.600000000000 1762280 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": 1274987, "vin": [ { "gen": { "height": 1274977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6a2de84fdef24cf83b01d0276f934e46eeb9d3473909f24a9ee63fb8d247501" } } ], "extra": [ 1, 212, 229, 222, 125, 11, 155, 182, 226, 188, 131, 160, 198, 128, 238, 229, 124, 150, 116, 167, 87, 247, 216, 185, 250, 165, 75, 212, 210, 41, 180, 64, 227, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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