Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dd10a5552b624808ce94dbc9d7f4d7ac783eeb5bb404855fa48a5de2a2422c1

Tx prefix hash: b21825c045bc3d732ee0ae79e69c7c0e3ba3566c7f9dae09b543745a1756d87c
Tx public key: cf1501f91242934726fe4dee214381a897e64f5f6ed60cdfd1ffde34b1479bb8
Timestamp: 1586615450 Timestamp [UTC]: 2020-04-11 14:30:50 Age [y:d:h:m:s]: 06:224:18:08:19
Block: 92459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1590830 RingCT/type: yes/0
Extra: 01cf1501f91242934726fe4dee214381a897e64f5f6ed60cdfd1ffde34b1479bb80211000000966fa03929000000000000000000

1 output(s) for total of 0.303141728867 xmr

stealth address amount amount idx tag
00: 020227f3fc0a07b623e7f0e33a3877576ed47f4c2145025480acdc5c1bcc2d16 0.303141728867 165083 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": 92469, "vin": [ { "gen": { "height": 92459 } } ], "vout": [ { "amount": 303141728867, "target": { "key": "020227f3fc0a07b623e7f0e33a3877576ed47f4c2145025480acdc5c1bcc2d16" } } ], "extra": [ 1, 207, 21, 1, 249, 18, 66, 147, 71, 38, 254, 77, 238, 33, 67, 129, 168, 151, 230, 79, 95, 110, 214, 12, 223, 209, 255, 222, 52, 177, 71, 155, 184, 2, 17, 0, 0, 0, 150, 111, 160, 57, 41, 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: