Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d1d6268c238bbd4c811fbad5450ec841f4fe730524f8ad19d4dfcc84fc47aa

Tx prefix hash: c366d3260cd421ce8a2ab48b16e18e6fba0ec39444d927135255fc8e7974cee2
Tx public key: 05e9e2faedb472ba22140a1565f8766bcee676b9f9e384c15c3dbe0b60281e16
Timestamp: 1733270626 Timestamp [UCT]: 2024-12-04 00:03:46 Age [y:d:h:m:s]: 00:117:14:33:24
Block: 1167477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83844 RingCT/type: yes/0
Extra: 0105e9e2faedb472ba22140a1565f8766bcee676b9f9e384c15c3dbe0b60281e1602110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d931b0ff64bbe90b4b656205a2d937494f1372b283328a4516abf9914406437 0.600000000000 1653174 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": 1167487, "vin": [ { "gen": { "height": 1167477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d931b0ff64bbe90b4b656205a2d937494f1372b283328a4516abf9914406437" } } ], "extra": [ 1, 5, 233, 226, 250, 237, 180, 114, 186, 34, 20, 10, 21, 101, 248, 118, 107, 206, 230, 118, 185, 249, 227, 132, 193, 92, 61, 190, 11, 96, 40, 30, 22, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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