Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05fbe12c4f8d2e4d5349312181a66d55b03cbef1aec9cbe4ace500e29c64d6c1

Tx prefix hash: f7987fe1aec2a25daec9c73dfad31e107f3dda16ab0b1171a1be6aa00f05681d
Tx public key: 859551e1d47fe96c700c23dea85e6a3c800d966ef4dfb5f2beb5c94d0b9c6a2d
Timestamp: 1777043781 Timestamp [UTC]: 2026-04-24 15:16:21 Age [y:d:h:m:s]: 00:210:23:31:01
Block: 1519295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 164182 RingCT/type: yes/0
Extra: 01859551e1d47fe96c700c23dea85e6a3c800d966ef4dfb5f2beb5c94d0b9c6a2d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: db64f9c9e2bd8e9b3e94cd23e3df6a9e6321859725025081d433684b2792ec2d 0.000600000000 2009145 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": 1519305, "vin": [ { "gen": { "height": 1519295 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "db64f9c9e2bd8e9b3e94cd23e3df6a9e6321859725025081d433684b2792ec2d", "view_tag": "51" } } } ], "extra": [ 1, 133, 149, 81, 225, 212, 127, 233, 108, 112, 12, 35, 222, 168, 94, 106, 60, 128, 13, 150, 110, 244, 223, 181, 242, 190, 181, 201, 77, 11, 156, 106, 45 ], "rct_signatures": { "type": 0 } }


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