Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6374fb0cfd43a528ec87e7943ef88a6dce405bae25e7a71c4791435959de4c34

Tx prefix hash: fccf8e0de4dc3d80849344df60cb793fb0f938b53125ba98eb4dee9dffe7a0b1
Tx public key: 7246b61c78ae14ac493be9ac06befc1ef24c412cd62bdde882d4ffd87a73c1f0
Timestamp: 1608262318 Timestamp [UTC]: 2020-12-18 03:31:58 Age [y:d:h:m:s]: 05:281:10:10:21
Block: 164284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1478289 RingCT/type: yes/0
Extra: 017246b61c78ae14ac493be9ac06befc1ef24c412cd62bdde882d4ffd87a73c1f00211000000314ea414e5000000000000000000

1 output(s) for total of 0.175253658694 xmr

stealth address amount amount idx tag
00: 8a54979665526bd560ef3a7e87456c5da99ea1c79a1e244bea93fe19e5b61141 0.175253658694 296805 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": 164294, "vin": [ { "gen": { "height": 164284 } } ], "vout": [ { "amount": 175253658694, "target": { "key": "8a54979665526bd560ef3a7e87456c5da99ea1c79a1e244bea93fe19e5b61141" } } ], "extra": [ 1, 114, 70, 182, 28, 120, 174, 20, 172, 73, 59, 233, 172, 6, 190, 252, 30, 242, 76, 65, 44, 214, 43, 221, 232, 130, 212, 255, 216, 122, 115, 193, 240, 2, 17, 0, 0, 0, 49, 78, 164, 20, 229, 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: