Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b377152922a0624e3c59a281236ab5d6da2c382e201ff598e4e0221e2d2251d

Tx prefix hash: d64b18fe0f6f0023ddb2048443cd8573fa96a7d2857ea488fc3c1e01d6f4af46
Tx public key: f4e0600732f0b045e4e864d012fc80afaf5dca87014099f2ca95d8590a8f789d
Timestamp: 1726492174 Timestamp [UCT]: 2024-09-16 13:09:34 Age [y:d:h:m:s]: 00:114:12:46:38
Block: 1111386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81897 RingCT/type: yes/0
Extra: 01f4e0600732f0b045e4e864d012fc80afaf5dca87014099f2ca95d8590a8f789d02110000001be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9833d3a0025796bb25a388c5cd8a2c68f34d07a5254fcf172c895e5fce7c3ee8 0.600000000000 1590321 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": 1111396, "vin": [ { "gen": { "height": 1111386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9833d3a0025796bb25a388c5cd8a2c68f34d07a5254fcf172c895e5fce7c3ee8" } } ], "extra": [ 1, 244, 224, 96, 7, 50, 240, 176, 69, 228, 232, 100, 208, 18, 252, 128, 175, 175, 93, 202, 135, 1, 64, 153, 242, 202, 149, 216, 89, 10, 143, 120, 157, 2, 17, 0, 0, 0, 27, 233, 20, 221, 21, 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