Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288446c2966029fc705ce57dc5324d3a6f2d3cf4a2320100e0b8015afdb56944

Tx prefix hash: 1085033859df7ad882a50b6025836d54ee38ae7800fa59a01ae3c2f90d69bf1a
Tx public key: 618cfe280682e34cc1314f7b349e2e87056cdeb7d8162a53d32b3dbb07225d6b
Timestamp: 1771396253 Timestamp [UTC]: 2026-02-18 06:30:53 Age [y:d:h:m:s]: 00:273:08:37:11
Block: 1480287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200913 RingCT/type: yes/0
Extra: 01618cfe280682e34cc1314f7b349e2e87056cdeb7d8162a53d32b3dbb07225d6b021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c429485f3d7c60c4813fa8aec51aef46cdf7cf5a8088894da3f0b098edefeb66 0.000600000000 1969655 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": 1480297, "vin": [ { "gen": { "height": 1480287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c429485f3d7c60c4813fa8aec51aef46cdf7cf5a8088894da3f0b098edefeb66" } } ], "extra": [ 1, 97, 140, 254, 40, 6, 130, 227, 76, 193, 49, 79, 123, 52, 158, 46, 135, 5, 108, 222, 183, 216, 22, 42, 83, 211, 43, 61, 187, 7, 34, 93, 107, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: