Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e0dc937f3d5fc485c7376d2a6f3399cb6fd0e664e8e8fb2604402240be52197

Tx prefix hash: e0848f29b3edbd6bc37bba2b709c3e2c8ca79bc7fcfdb51ab982ab550a11f1a4
Tx public key: 0711a684ce21e88ed54cdd6d604efa0e709965fc7d5a4ec8b2b0943468c67d7b
Timestamp: 1735996435 Timestamp [UCT]: 2025-01-04 13:13:55 Age [y:d:h:m:s]: 00:346:23:16:16
Block: 1190045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245521 RingCT/type: yes/0
Extra: 010711a684ce21e88ed54cdd6d604efa0e709965fc7d5a4ec8b2b0943468c67d7b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c45f400d102ed051d64e872081d1c73011696dac22f86cad1bf0dc1b07f57446 0.600000000000 1676560 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": 1190055, "vin": [ { "gen": { "height": 1190045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c45f400d102ed051d64e872081d1c73011696dac22f86cad1bf0dc1b07f57446" } } ], "extra": [ 1, 7, 17, 166, 132, 206, 33, 232, 142, 213, 76, 221, 109, 96, 78, 250, 14, 112, 153, 101, 252, 125, 90, 78, 200, 178, 176, 148, 52, 104, 198, 125, 123, 2, 17, 0, 0, 0, 3, 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