Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04fe1a2c89627070d29c2e2ba41dd5dd5d470761901cfd5320f578031c0e12dd

Tx prefix hash: b5baafae4e7a0f6af15c16c080126b1526bf352854c615426b85fc943f308da7
Tx public key: 6d6fe13fddacf31980717d6cd8ecedf807efd422c7b2b0d3622d0347939d76e9
Timestamp: 1758076787 Timestamp [UTC]: 2025-09-17 02:39:47 Age [y:d:h:m:s]: 00:241:21:02:07
Block: 1370111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165342 RingCT/type: yes/0
Extra: 016d6fe13fddacf31980717d6cd8ecedf807efd422c7b2b0d3622d0347939d76e9021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88f7a3bf2d7a8c9c44ea4fa1c421071fd0cbebd878358f05ffe55fcba67f7daa 0.000600000000 1858186 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": 1370121, "vin": [ { "gen": { "height": 1370111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88f7a3bf2d7a8c9c44ea4fa1c421071fd0cbebd878358f05ffe55fcba67f7daa" } } ], "extra": [ 1, 109, 111, 225, 63, 221, 172, 243, 25, 128, 113, 125, 108, 216, 236, 237, 248, 7, 239, 212, 34, 199, 178, 176, 211, 98, 45, 3, 71, 147, 157, 118, 233, 2, 17, 0, 0, 0, 2, 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: