Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b30cfd286168209d5ff7012bd93141bd6947db0de199a33570a980ff0346aa07

Tx prefix hash: ae981c8831ac00e07d5fe378b961e1cb500440dec582e7e1213e693ae72eef90
Tx public key: 685bd2182e21eaa96f2da28b466d5eb81372147fd99418e5d76956f5e1526aa3
Timestamp: 1697573573 Timestamp [UTC]: 2023-10-17 20:12:53 Age [y:d:h:m:s]: 02:312:06:41:00
Block: 871830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 748557 RingCT/type: yes/0
Extra: 01685bd2182e21eaa96f2da28b466d5eb81372147fd99418e5d76956f5e1526aa302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.000792985636 xmr

stealth address amount amount idx tag
00: 10ef06790954ac9b336fef8f4f7194c780f7bb5258a88e3ce852d80ffce9e917 0.000792985636 1326861 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": 871840, "vin": [ { "gen": { "height": 871830 } } ], "vout": [ { "amount": 792985636, "target": { "key": "10ef06790954ac9b336fef8f4f7194c780f7bb5258a88e3ce852d80ffce9e917" } } ], "extra": [ 1, 104, 91, 210, 24, 46, 33, 234, 169, 111, 45, 162, 139, 70, 109, 94, 184, 19, 114, 20, 127, 217, 148, 24, 229, 215, 105, 86, 245, 225, 82, 106, 163, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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: