Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c9e03a5f19f4bc472c2b90d1c769970116f7741b83fdbd535a0fd6cb5208eac

Tx prefix hash: 0d7adf640e140ceba15cd4f350ef166d09858f2ee4a6e5e4d6bd2945c5441f34
Tx public key: 0a0ab225530a6dcd716e06c48fb79e14a2ac296123a0f1323bcf9d9d227bd78e
Timestamp: 1704675596 Timestamp [UCT]: 2024-01-08 00:59:56 Age [y:d:h:m:s]: 01:303:03:41:26
Block: 930484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475481 RingCT/type: yes/0
Extra: 010a0ab225530a6dcd716e06c48fb79e14a2ac296123a0f1323bcf9d9d227bd78e02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c7e4c002af7ce50c4a8aa8fe56dd68e8a5633e865c0518cfe17b55036698c4 0.600000000000 1388366 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": 930494, "vin": [ { "gen": { "height": 930484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c7e4c002af7ce50c4a8aa8fe56dd68e8a5633e865c0518cfe17b55036698c4" } } ], "extra": [ 1, 10, 10, 178, 37, 83, 10, 109, 205, 113, 110, 6, 196, 143, 183, 158, 20, 162, 172, 41, 97, 35, 160, 241, 50, 59, 207, 157, 157, 34, 123, 215, 142, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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