Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af430ba3f01cbfead5c16b640b5b7ee70ca89e48cbe21a3f283e5868a2845d71

Tx prefix hash: 79ade1775311c7edb99d286311ad7b479bb02096e8c1b1e3191a7eb00778d7e0
Tx public key: ef8d24d5ece2dac2903a97407ed9a2ea70204171f12aadfef807905ae53593f8
Timestamp: 1764091285 Timestamp [UTC]: 2025-11-25 17:21:25 Age [y:d:h:m:s]: 00:358:07:05:19
Block: 1419966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261539 RingCT/type: yes/0
Extra: 01ef8d24d5ece2dac2903a97407ed9a2ea70204171f12aadfef807905ae53593f802110000000217b19132000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ec3f26750fe8692f42a8093c5857f9ff8a6e2504785b1675fe320128b96a582a 0.000600000000 1908507 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": 1419976, "vin": [ { "gen": { "height": 1419966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec3f26750fe8692f42a8093c5857f9ff8a6e2504785b1675fe320128b96a582a" } } ], "extra": [ 1, 239, 141, 36, 213, 236, 226, 218, 194, 144, 58, 151, 64, 126, 217, 162, 234, 112, 32, 65, 113, 241, 42, 173, 254, 248, 7, 144, 90, 229, 53, 147, 248, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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: