Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3397d40c2ca1554cf63e38b26472ed5514ab664f62064887ef357e4bebbef818

Tx prefix hash: 00a147995360680fbf1951bc3d2e332943cbbfea4b2fe0c787bc33e0a40b5aae
Tx public key: aa4d9744ac67f2d6253dd957600b5cf8fba5ef898d554558d2bbc7a3f39dd3bf
Timestamp: 1721336498 Timestamp [UTC]: 2024-07-18 21:01:38 Age [y:d:h:m:s]: 01:305:05:38:43
Block: 1068646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470034 RingCT/type: yes/0
Extra: 01aa4d9744ac67f2d6253dd957600b5cf8fba5ef898d554558d2bbc7a3f39dd3bf02110000000291e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 920238d99d2e24736ce8bdd30c5648858b5d0ef6d830777b6e66ac2d41db89ac 0.000600000000 1539759 of 15 -

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": 1068656, "vin": [ { "gen": { "height": 1068646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "920238d99d2e24736ce8bdd30c5648858b5d0ef6d830777b6e66ac2d41db89ac" } } ], "extra": [ 1, 170, 77, 151, 68, 172, 103, 242, 214, 37, 61, 217, 87, 96, 11, 92, 248, 251, 165, 239, 137, 141, 85, 69, 88, 210, 187, 199, 163, 243, 157, 211, 191, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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: