Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30de9e94213d3369dbb670c2cb21e9fd67eb7566324b7640cdc7baaee9f5c234

Tx prefix hash: 91d4602702a1f8c3e4c708cc89a01e28bea6685db0277d2e9201d3830dea94c8
Tx public key: 774f3dbb9120b5c20ebaad9d5c47c0806f06d25eb5db48cda8c61399d8aa3fc4
Timestamp: 1583457386 Timestamp [UTC]: 2020-03-06 01:16:26 Age [y:d:h:m:s]: 06:075:02:24:10
Block: 77219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1460447 RingCT/type: yes/0
Extra: 01774f3dbb9120b5c20ebaad9d5c47c0806f06d25eb5db48cda8c61399d8aa3fc40211000000054ac5aa02000000000000000000

1 output(s) for total of 0.340519660628 xmr

stealth address amount amount idx tag
00: 7e039b89dc06e06681b3d98e661cebc4f037f1670eba5fe52b3da80d45321b49 0.340519660628 142106 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": 77229, "vin": [ { "gen": { "height": 77219 } } ], "vout": [ { "amount": 340519660628, "target": { "key": "7e039b89dc06e06681b3d98e661cebc4f037f1670eba5fe52b3da80d45321b49" } } ], "extra": [ 1, 119, 79, 61, 187, 145, 32, 181, 194, 14, 186, 173, 157, 92, 71, 192, 128, 111, 6, 210, 94, 181, 219, 72, 205, 168, 198, 19, 153, 216, 170, 63, 196, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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: