Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3219aead86a4364f2208d9780febf9e4025a725ed3f82aaa3fdb847a962ee1fb

Tx prefix hash: e23c5579503f524281951fe2a2d7a1858878c9a4207ed74513b548a6ed9725df
Tx public key: 4528c300840fc0b15db32deb625be6e6e8cea6c8ba8a0bad6db0e8662a8001e6
Timestamp: 1759156965 Timestamp [UTC]: 2025-09-29 14:42:45 Age [y:d:h:m:s]: 00:263:18:48:42
Block: 1379071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184666 RingCT/type: yes/0
Extra: 014528c300840fc0b15db32deb625be6e6e8cea6c8ba8a0bad6db0e8662a8001e602110000000a97baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66b4650d6715de5ab6e80a8d92327df9128cf7c3b6d9661e63378441d3024812 0.000600000000 1867168 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": 1379081, "vin": [ { "gen": { "height": 1379071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b4650d6715de5ab6e80a8d92327df9128cf7c3b6d9661e63378441d3024812" } } ], "extra": [ 1, 69, 40, 195, 0, 132, 15, 192, 177, 93, 179, 45, 235, 98, 91, 230, 230, 232, 206, 166, 200, 186, 138, 11, 173, 109, 176, 232, 102, 42, 128, 1, 230, 2, 17, 0, 0, 0, 10, 151, 186, 249, 34, 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: