Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a28aa7a3bfc5bf0dd349759fc91df6ef6b858b78f35e7b9f148308cf6a2df63

Tx prefix hash: b77d298bb87fe4163a4e02fab8b371cfff56f551dc2609c13d24a4ed915f8274
Tx public key: 0ad663e445e081218b6fd05981464523e9bbb07a52a1c55b4a9bbb905ba6dfd2
Timestamp: 1756126034 Timestamp [UTC]: 2025-08-25 12:47:14 Age [y:d:h:m:s]: 01:081:13:36:37
Block: 1354135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324434 RingCT/type: yes/0
Extra: 010ad663e445e081218b6fd05981464523e9bbb07a52a1c55b4a9bbb905ba6dfd20211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e640e309b9dc5754ddb46fe28f209cd1736fed67b2a86500c29a4b00e56b796 0.000600000000 1842116 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": 1354145, "vin": [ { "gen": { "height": 1354135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e640e309b9dc5754ddb46fe28f209cd1736fed67b2a86500c29a4b00e56b796" } } ], "extra": [ 1, 10, 214, 99, 228, 69, 224, 129, 33, 139, 111, 208, 89, 129, 70, 69, 35, 233, 187, 176, 122, 82, 161, 197, 91, 74, 155, 187, 144, 91, 166, 223, 210, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: