Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db095680ae3144c8f2ebcb07361c0740d56c6494a3aa7ae60a9c91f44f076f4e

Tx prefix hash: d918b58e569e6625de8eaa028ed958c000b9436d14cec12901c5a1399af43f61
Tx public key: 0d47c7757ef3dad1ed6b5fb6fcaba4ab7be24eb78ccdba71cc7d2f42f9115ccd
Timestamp: 1699481125 Timestamp [UCT]: 2023-11-08 22:05:25 Age [y:d:h:m:s]: 01:155:22:51:14
Block: 887449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372645 RingCT/type: yes/0
Extra: 010d47c7757ef3dad1ed6b5fb6fcaba4ab7be24eb78ccdba71cc7d2f42f9115ccd021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.703903407000 dcy

stealth address amount amount idx
00: 0ac16d5d5f35b96e0fa01e1b13a8ecc44c5316d2dd81dcb2ed1594aefdf95623 0.703903407000 1343332 of 0

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": 887459, "vin": [ { "gen": { "height": 887449 } } ], "vout": [ { "amount": 703903407, "target": { "key": "0ac16d5d5f35b96e0fa01e1b13a8ecc44c5316d2dd81dcb2ed1594aefdf95623" } } ], "extra": [ 1, 13, 71, 199, 117, 126, 243, 218, 209, 237, 107, 95, 182, 252, 171, 164, 171, 123, 226, 78, 183, 140, 205, 186, 113, 204, 125, 47, 66, 249, 17, 92, 205, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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