Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d191762ca1aed9675fe31362d2d346068ebe70ea173773ab3638c5cc1e36862a

Tx prefix hash: ef024d44711cc952225d5bfd69d9098f0840c3f357a943f20aaecfdd466016ca
Tx public key: 91c4dfe1b7b8c2112355bcb74ff270773c539fbfd7d2b7e5e3c1f3b3bc9dde2c
Timestamp: 1734285644 Timestamp [UCT]: 2024-12-15 18:00:44 Age [y:d:h:m:s]: 00:115:14:28:07
Block: 1175899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82396 RingCT/type: yes/0
Extra: 0191c4dfe1b7b8c2112355bcb74ff270773c539fbfd7d2b7e5e3c1f3b3bc9dde2c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8364670c85c39636858504dae7d46535dd9dab78b75e6662071700eaa7bae41a 0.600000000000 1662226 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": 1175909, "vin": [ { "gen": { "height": 1175899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8364670c85c39636858504dae7d46535dd9dab78b75e6662071700eaa7bae41a" } } ], "extra": [ 1, 145, 196, 223, 225, 183, 184, 194, 17, 35, 85, 188, 183, 79, 242, 112, 119, 60, 83, 159, 191, 215, 210, 183, 229, 227, 193, 243, 179, 188, 157, 222, 44, 2, 17, 0, 0, 0, 5, 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