Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 011ff4d42a98c444d4b47ff0e0ba72fa99dd6c6d5f6cb3d269b33f58820d7eaf

Tx prefix hash: 6725af1255264feef09d9e197afbd6f7d68c2f0bf32f6a2d46a8fbd3020bd4fb
Tx public key: 839f9d5adf66894c4be4f572af12d2bc4b8991fc87454d9be2e8883c99a42be1
Timestamp: 1712450934 Timestamp [UCT]: 2024-04-07 00:48:54 Age [y:d:h:m:s]: 01:298:02:12:06
Block: 994937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471687 RingCT/type: yes/0
Extra: 01839f9d5adf66894c4be4f572af12d2bc4b8991fc87454d9be2e8883c99a42be1021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d7e14e0969eb2d62296dcd6ecbd8b794fc8ac4a3bffd27df0d93de4f4f954a 0.600000000000 1455341 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": 994947, "vin": [ { "gen": { "height": 994937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d7e14e0969eb2d62296dcd6ecbd8b794fc8ac4a3bffd27df0d93de4f4f954a" } } ], "extra": [ 1, 131, 159, 157, 90, 223, 102, 137, 76, 75, 228, 245, 114, 175, 18, 210, 188, 75, 137, 145, 252, 135, 69, 77, 155, 226, 232, 136, 60, 153, 164, 43, 225, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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