Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc0bec89cc9dfebfafaf6564fb5ad41d617c2a249ec6642ff344b6a92477674

Tx prefix hash: a89984cb2ec64f919175087ef4b068e07a89a00f63908f2988eafaa3b9e4bad5
Tx public key: 9390c1ea1c6b3f7768cb1bb4157f9141297f8ce8ab771f0c678a3cf820587b03
Timestamp: 1630356632 Timestamp [UTC]: 2021-08-30 20:50:32 Age [y:d:h:m:s]: 04:254:22:36:42
Block: 324101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207437 RingCT/type: yes/0
Extra: 019390c1ea1c6b3f7768cb1bb4157f9141297f8ce8ab771f0c678a3cf820587b0302110000000548397882000000000000000000

1 output(s) for total of 0.051775803899 xmr

stealth address amount amount idx tag
00: f1a0c9e93231f45c93386315194a1d322aec7c4031eae00c1ec95755c3d5c639 0.051775803899 672074 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": 324111, "vin": [ { "gen": { "height": 324101 } } ], "vout": [ { "amount": 51775803899, "target": { "key": "f1a0c9e93231f45c93386315194a1d322aec7c4031eae00c1ec95755c3d5c639" } } ], "extra": [ 1, 147, 144, 193, 234, 28, 107, 63, 119, 104, 203, 27, 180, 21, 127, 145, 65, 41, 127, 140, 232, 171, 119, 31, 12, 103, 138, 60, 248, 32, 88, 123, 3, 2, 17, 0, 0, 0, 5, 72, 57, 120, 130, 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: