Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff81ee1e5049f0ded065db76ae66ad22e09bba0a575d175db7fd847d9420fe4

Tx prefix hash: ac7a61fb5def82dec9a3a31fc1180fae2d9e8a9492c505c5728864c0b5ddd7be
Tx public key: 790e07bb21c001abfe3182cb519f953278e7d6b0b342bb2f50969ead7c18adcc
Timestamp: 1634811352 Timestamp [UTC]: 2021-10-21 10:15:52 Age [y:d:h:m:s]: 05:030:12:46:54
Block: 357388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1324836 RingCT/type: yes/0
Extra: 01790e07bb21c001abfe3182cb519f953278e7d6b0b342bb2f50969ead7c18adcc02110000001e4a0f5013000000000000000000

1 output(s) for total of 0.040162950497 xmr

stealth address amount amount idx tag
00: 16447e21dbf638944a98c3ebc3b0687ef585acf678624f82c1a1dbd948102598 0.040162950497 728764 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": 357398, "vin": [ { "gen": { "height": 357388 } } ], "vout": [ { "amount": 40162950497, "target": { "key": "16447e21dbf638944a98c3ebc3b0687ef585acf678624f82c1a1dbd948102598" } } ], "extra": [ 1, 121, 14, 7, 187, 33, 192, 1, 171, 254, 49, 130, 203, 81, 159, 149, 50, 120, 231, 214, 176, 179, 66, 187, 47, 80, 150, 158, 173, 124, 24, 173, 204, 2, 17, 0, 0, 0, 30, 74, 15, 80, 19, 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: