Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a569768dbdecab12376d223e3952d9f5de15dc3fabac92bda94b87cea9c05d9

Tx prefix hash: 64c5cc286e846d91250590dfda8ea842d08942e1f7d59a3ea01a409ddf8c3b4f
Tx public key: ab3924ceefb3b5a77a6676ef683c86c9d552cdb09d598b4aefd0b7e38597f31e
Timestamp: 1582978442 Timestamp [UTC]: 2020-02-29 12:14:02 Age [y:d:h:m:s]: 06:080:13:44:28
Block: 74077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1463235 RingCT/type: yes/0
Extra: 01ab3924ceefb3b5a77a6676ef683c86c9d552cdb09d598b4aefd0b7e38597f31e02110000000b4943cd9f000000000000000000

1 output(s) for total of 0.348781103021 xmr

stealth address amount amount idx tag
00: 78bab36b4d5e9318c3c189b12f6b5c8ef323710fb17a3d11a9fa9a1128b6fad5 0.348781103021 136904 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": 74087, "vin": [ { "gen": { "height": 74077 } } ], "vout": [ { "amount": 348781103021, "target": { "key": "78bab36b4d5e9318c3c189b12f6b5c8ef323710fb17a3d11a9fa9a1128b6fad5" } } ], "extra": [ 1, 171, 57, 36, 206, 239, 179, 181, 167, 122, 102, 118, 239, 104, 60, 134, 201, 213, 82, 205, 176, 157, 89, 139, 74, 239, 208, 183, 227, 133, 151, 243, 30, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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: