Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c2ff2cc6e1a0921bafdaba99e9870e870e97f4491708f33ecc28850c3d45aa4

Tx prefix hash: bf7e007efc948fb27657af0ae1e9dedbaa4f3cfc0c3a85d2fb1e82bdc3afb2ef
Tx public key: beec3194fea6cecc2f1fb15de3a6b8074a9f8082559f1417561c3f5a73538883
Timestamp: 1742921862 Timestamp [UTC]: 2025-03-25 16:57:42 Age [y:d:h:m:s]: 01:240:18:51:58
Block: 1247101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436286 RingCT/type: yes/0
Extra: 01beec3194fea6cecc2f1fb15de3a6b8074a9f8082559f1417561c3f5a73538883021100000004c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 383513c266f6f965fb9b59f615a9a2c537219b4868c6d14fd28a32fb485ec894 0.000600000000 1734102 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": 1247111, "vin": [ { "gen": { "height": 1247101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "383513c266f6f965fb9b59f615a9a2c537219b4868c6d14fd28a32fb485ec894" } } ], "extra": [ 1, 190, 236, 49, 148, 254, 166, 206, 204, 47, 31, 177, 93, 227, 166, 184, 7, 74, 159, 128, 130, 85, 159, 20, 23, 86, 28, 63, 90, 115, 83, 136, 131, 2, 17, 0, 0, 0, 4, 198, 116, 9, 88, 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: