Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5b8092f4dba6f68ef2a0cdd831cefbfd6e47f514cdd5bc8919e5dad17e9469

Tx prefix hash: 7a2ed1137c83b2c7a04a773467a94f2f7300a82ccc41a1340df13ca27cc0f1ae
Tx public key: 8047b829c27993cfca402d278f499effd689ffdaa4b09a8b3ad6c94d32120bf3
Timestamp: 1574753533 Timestamp [UTC]: 2019-11-26 07:32:13 Age [y:d:h:m:s]: 06:360:01:22:35
Block: 17730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1664039 RingCT/type: yes/0
Extra: 018047b829c27993cfca402d278f499effd689ffdaa4b09a8b3ad6c94d32120bf3021100000001f95225a5000000000000000000

1 output(s) for total of 0.536110150521 xmr

stealth address amount amount idx tag
00: 853ab2a015555c516c6d26eab4424fa410d6d6326cd3921d112bc2b82c8e9727 0.536110150521 26194 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": 17740, "vin": [ { "gen": { "height": 17730 } } ], "vout": [ { "amount": 536110150521, "target": { "key": "853ab2a015555c516c6d26eab4424fa410d6d6326cd3921d112bc2b82c8e9727" } } ], "extra": [ 1, 128, 71, 184, 41, 194, 121, 147, 207, 202, 64, 45, 39, 143, 73, 158, 255, 214, 137, 255, 218, 164, 176, 154, 139, 58, 214, 201, 77, 50, 18, 11, 243, 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: