Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45d15b99a0d2200408e4a4fd18d2499c8c9c0859855e53f05013fcc67d315c22

Tx prefix hash: 800a1b7bcd8a9224417986a649fec40d9821a0be5416cafd1f9577b4439b8591
Tx public key: dcfebc0cc80ac8e49ef1cc351b74e5612974cc7d3a861cb82c3bce22a94a0542
Timestamp: 1730133169 Timestamp [UCT]: 2024-10-28 16:32:49 Age [y:d:h:m:s]: 00:182:00:43:22
Block: 1141490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129949 RingCT/type: yes/0
Extra: 01dcfebc0cc80ac8e49ef1cc351b74e5612974cc7d3a861cb82c3bce22a94a0542021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3b345bdeb2e4622b1d9511ee667bfd42f1c06007a068e0f23cbc06a8f87494f 0.600000000000 1625297 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": 1141500, "vin": [ { "gen": { "height": 1141490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3b345bdeb2e4622b1d9511ee667bfd42f1c06007a068e0f23cbc06a8f87494f" } } ], "extra": [ 1, 220, 254, 188, 12, 200, 10, 200, 228, 158, 241, 204, 53, 27, 116, 229, 97, 41, 116, 204, 125, 58, 134, 28, 184, 44, 59, 206, 34, 169, 74, 5, 66, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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