Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c508f62839e378e9187b426fd1d5814dc7c2f20bd3371641ffbc562a6b33f143

Tx prefix hash: c8e26fddd0d9731c4298c6318cc2dbb5c569793e4e2c736df23b5f0d6b104e5f
Tx public key: 63239d038fa4b9361769df4d05d362d48b757549e58512e5ad8f3d2cc3ccaf09
Timestamp: 1696967047 Timestamp [UCT]: 2023-10-10 19:44:07 Age [y:d:h:m:s]: 01:159:04:59:34
Block: 866810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374824 RingCT/type: yes/0
Extra: 0163239d038fa4b9361769df4d05d362d48b757549e58512e5ad8f3d2cc3ccaf090211000000094b8f5122000000000000000000

1 output(s) for total of 0.823945853000 dcy

stealth address amount amount idx
00: f3bf07f45ba22d122649998f6ce5b7c9b21a55690b8fee5d0010192784f01292 0.823945853000 1321446 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": 866820, "vin": [ { "gen": { "height": 866810 } } ], "vout": [ { "amount": 823945853, "target": { "key": "f3bf07f45ba22d122649998f6ce5b7c9b21a55690b8fee5d0010192784f01292" } } ], "extra": [ 1, 99, 35, 157, 3, 143, 164, 185, 54, 23, 105, 223, 77, 5, 211, 98, 212, 139, 117, 117, 73, 229, 133, 18, 229, 173, 143, 61, 44, 195, 204, 175, 9, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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