Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a2107953795dc87f0c59f56d7c059f3e6666e221ebbac9ddc96f8135f2c94e4

Tx prefix hash: cf2370695b5db834941c3bc870cbf9e974cb77ce4aa041276131b5ddda1e8b75
Tx public key: 164799228bf0d214135836f742282b575807e54d6b75bd145a00d1553a22206b
Timestamp: 1584185310 Timestamp [UTC]: 2020-03-14 11:28:30 Age [y:d:h:m:s]: 06:252:17:11:35
Block: 82386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1600785 RingCT/type: yes/0
Extra: 01164799228bf0d214135836f742282b575807e54d6b75bd145a00d1553a22206b02110000000528db8c57000000000000000000

1 output(s) for total of 0.327357102778 xmr

stealth address amount amount idx tag
00: 3df55c4018e5a34b72f8b3d74a818c00ed69689929d8149d955fd22d5ce8f2fb 0.327357102778 150232 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": 82396, "vin": [ { "gen": { "height": 82386 } } ], "vout": [ { "amount": 327357102778, "target": { "key": "3df55c4018e5a34b72f8b3d74a818c00ed69689929d8149d955fd22d5ce8f2fb" } } ], "extra": [ 1, 22, 71, 153, 34, 139, 240, 210, 20, 19, 88, 54, 247, 66, 40, 43, 87, 88, 7, 229, 77, 107, 117, 189, 20, 90, 0, 209, 85, 58, 34, 32, 107, 2, 17, 0, 0, 0, 5, 40, 219, 140, 87, 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: