Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c715288fe42e2415b8946e8ee914dcf383b6881de3411201c95f6053bccfe29

Tx prefix hash: 636198dd738e0affe1e7f917629da650061543fbc659b5d307c6c8944b76cc09
Tx public key: e020cb340710db419bc3bb0d2c1271f1c807eb03b625fd93ccf967dd5ef99480
Timestamp: 1742728408 Timestamp [UTC]: 2025-03-23 11:13:28 Age [y:d:h:m:s]: 01:243:15:51:16
Block: 1245517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437977 RingCT/type: yes/0
Extra: 01e020cb340710db419bc3bb0d2c1271f1c807eb03b625fd93ccf967dd5ef9948002110000000baf845649000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6702fd8378316dc3f9216b29f7d2c618d0dd9a30ac525ef4b0033f2ed3efbe37 0.000600000000 1732508 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": 1245527, "vin": [ { "gen": { "height": 1245517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6702fd8378316dc3f9216b29f7d2c618d0dd9a30ac525ef4b0033f2ed3efbe37" } } ], "extra": [ 1, 224, 32, 203, 52, 7, 16, 219, 65, 155, 195, 187, 13, 44, 18, 113, 241, 200, 7, 235, 3, 182, 37, 253, 147, 204, 249, 103, 221, 94, 249, 148, 128, 2, 17, 0, 0, 0, 11, 175, 132, 86, 73, 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: