Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f8387bc29cf3113ed933e52c585ce3ec7c43c38d24f7916d4485cee24482ee

Tx prefix hash: d2e7403ff4f554fde182e1a097b8dc88883f7b703cd65e937914b59cd6bffd2e
Tx public key: 68c358f015a7f854ed925c2456853d66abe1bf194cdc2a477aa4e707787b19b3
Timestamp: 1636957835 Timestamp [UTC]: 2021-11-15 06:30:35 Age [y:d:h:m:s]: 04:178:22:50:45
Block: 374649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157222 RingCT/type: yes/0
Extra: 0168c358f015a7f854ed925c2456853d66abe1bf194cdc2a477aa4e707787b19b302110000000ca272b9cb000000000000000000

1 output(s) for total of 0.035207300437 xmr

stealth address amount amount idx tag
00: a6f2c1225bd2af5ffb7eee02f46bf0b40c01bf71d2e9d3aed6da2f9c6b361468 0.035207300437 758265 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 dinastycoin-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": 374659, "vin": [ { "gen": { "height": 374649 } } ], "vout": [ { "amount": 35207300437, "target": { "key": "a6f2c1225bd2af5ffb7eee02f46bf0b40c01bf71d2e9d3aed6da2f9c6b361468" } } ], "extra": [ 1, 104, 195, 88, 240, 21, 167, 248, 84, 237, 146, 92, 36, 86, 133, 61, 102, 171, 225, 191, 25, 76, 220, 42, 71, 122, 164, 231, 7, 120, 123, 25, 179, 2, 17, 0, 0, 0, 12, 162, 114, 185, 203, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: