Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f4ea69e2d4cd8bd90e49364d90f1b2be21840c0296e3792d5397374e6c6be8

Tx prefix hash: 4edf87eadc92690d428ad49a4598bf189614f17a8330aa163a1cc080a02adfc6
Tx public key: 16d80fcd1ad1abdd39eb06bd39e3c3d50bf9629f493bdf57884ce0139193d44f
Timestamp: 1771125141 Timestamp [UTC]: 2026-02-15 03:12:21 Age [y:d:h:m:s]: 00:275:06:52:46
Block: 1478057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202254 RingCT/type: yes/0
Extra: 0116d80fcd1ad1abdd39eb06bd39e3c3d50bf9629f493bdf57884ce0139193d44f021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 89340be0cfe41110727cd59b246c1eaf54ed01a945ccce691a738396e8ea7c21 0.000600000000 1967379 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": 1478067, "vin": [ { "gen": { "height": 1478057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89340be0cfe41110727cd59b246c1eaf54ed01a945ccce691a738396e8ea7c21" } } ], "extra": [ 1, 22, 216, 15, 205, 26, 209, 171, 221, 57, 235, 6, 189, 57, 227, 195, 213, 11, 249, 98, 159, 73, 59, 223, 87, 136, 76, 224, 19, 145, 147, 212, 79, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: