Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bb5b4555056667532fd8727f57ed1a1f422e599c087e5d4b7ef4b3cfbf4c7d2

Tx prefix hash: 24546d276fd26661570830db91e7b3b4e1e431b861ce90b66b388e7d9ebddf12
Tx public key: aa6acbc7bf8279f51638848beccd10436b555dede4996e9bd910d9bac8746249
Timestamp: 1758310156 Timestamp [UTC]: 2025-09-19 19:29:16 Age [y:d:h:m:s]: 01:063:09:02:28
Block: 1372051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311443 RingCT/type: yes/0
Extra: 01aa6acbc7bf8279f51638848beccd10436b555dede4996e9bd910d9bac8746249021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ceba7249a3b1a9b0fc8e0420a50fcc5ac11a16ea2c413edc147b8d2fb53230e2 0.000600000000 1860136 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": 1372061, "vin": [ { "gen": { "height": 1372051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceba7249a3b1a9b0fc8e0420a50fcc5ac11a16ea2c413edc147b8d2fb53230e2" } } ], "extra": [ 1, 170, 106, 203, 199, 191, 130, 121, 245, 22, 56, 132, 139, 236, 205, 16, 67, 107, 85, 93, 237, 228, 153, 110, 155, 217, 16, 217, 186, 200, 116, 98, 73, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: