Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8257063ec4b0fffa04c061dbb529f31fc3b9baa1e3e8477b8acaed254f00c9a

Tx prefix hash: 066091191d110956c2b42e67d4a65d54ea8c602ddcbeab6e1c66cb2098de16bd
Tx public key: faef770bf6c93f9704fc8b6e3e8f747fd8dda2a372f09a75add4bb1e08347ea6
Timestamp: 1670265485 Timestamp [UTC]: 2022-12-05 18:38:05 Age [y:d:h:m:s]: 03:163:13:30:37
Block: 646129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 889598 RingCT/type: yes/0
Extra: 01faef770bf6c93f9704fc8b6e3e8f747fd8dda2a372f09a75add4bb1e08347ea602110000000183600029000000000000000000

1 output(s) for total of 0.004437173333 xmr

stealth address amount amount idx tag
00: a730526f2fe9072fb9779db8824b669bc33c1eff617d10ddcc7e07d18d37cc34 0.004437173333 1086340 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": 646139, "vin": [ { "gen": { "height": 646129 } } ], "vout": [ { "amount": 4437173333, "target": { "key": "a730526f2fe9072fb9779db8824b669bc33c1eff617d10ddcc7e07d18d37cc34" } } ], "extra": [ 1, 250, 239, 119, 11, 246, 201, 63, 151, 4, 252, 139, 110, 62, 143, 116, 127, 216, 221, 162, 163, 114, 240, 154, 117, 173, 212, 187, 30, 8, 52, 126, 166, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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: