Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f484b55ec99b24f3b6f1fa519d6e9d6d3dd704f0098940ba7d5685ce6d4a2e0

Tx prefix hash: 215735b8409ecf499365f507bc8368f9ea3fd3d5a6e67a5ae4dc8ae1d7e11ba4
Tx public key: 587ee4ef1d3d89c159e80217f420c7e0d9c6873c8d777ba8984ba4a7f968a300
Timestamp: 1794865126 Timestamp [UTC]: 2026-11-16 21:38:46 Age [y:d:h:m:s]: 00:004:12:33:42
Block: 1679924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 3420 RingCT/type: yes/0
Extra: 01587ee4ef1d3d89c159e80217f420c7e0d9c6873c8d777ba8984ba4a7f968a300

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 48d581e08a9c0d37bf16930b02add0dd2317bb113e5ce64cc888fd963a2d89fc 0.000600000000 2170712 of 15 <51>

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": 1679934, "vin": [ { "gen": { "height": 1679924 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "48d581e08a9c0d37bf16930b02add0dd2317bb113e5ce64cc888fd963a2d89fc", "view_tag": "51" } } } ], "extra": [ 1, 88, 126, 228, 239, 29, 61, 137, 193, 89, 232, 2, 23, 244, 32, 199, 224, 217, 198, 135, 60, 141, 119, 123, 168, 152, 75, 164, 167, 249, 104, 163, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: