Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13a5335779ca8a0dd461eac6daf35aa0c881016664bd49de2e21a4c02c7af6ec

Tx prefix hash: 84dfa749e8920b23cdcc65f651a9039fdf29ece322d944a9fb7a0e1a35c6c2f9
Tx public key: 07419470a587ac9e9443514dd48f8605535d82c34dc5f2838c9e15d453e21c68
Timestamp: 1574658863 Timestamp [UTC]: 2019-11-25 05:14:23 Age [y:d:h:m:s]: 06:364:07:53:43
Block: 16929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1666565 RingCT/type: yes/0
Extra: 0107419470a587ac9e9443514dd48f8605535d82c34dc5f2838c9e15d453e21c68021100000001f95225a5000000000000000000

1 output(s) for total of 0.539408391206 xmr

stealth address amount amount idx tag
00: f628ee67e8a71773548fd28c24ab39d2bc970f245d6390024f9b86451e85a764 0.539408391206 24113 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": 16939, "vin": [ { "gen": { "height": 16929 } } ], "vout": [ { "amount": 539408391206, "target": { "key": "f628ee67e8a71773548fd28c24ab39d2bc970f245d6390024f9b86451e85a764" } } ], "extra": [ 1, 7, 65, 148, 112, 165, 135, 172, 158, 148, 67, 81, 77, 212, 143, 134, 5, 83, 93, 130, 195, 77, 197, 242, 131, 140, 158, 21, 212, 83, 226, 28, 104, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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: