Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa33cc147ba09db83d9d5770fcc3595637b8d0a58af655a3d6d4ca57c10bdfb

Tx prefix hash: 96f70f8e48f9b741ccf2ef383e7b01d7908100e4e844554dbf3e337b5ff340a1
Tx public key: f519409a58ab3ba491159f1eb150586c58feea5a9ce9b23684cbe3acf0da86be
Timestamp: 1760905383 Timestamp [UTC]: 2025-10-19 20:23:03 Age [y:d:h:m:s]: 01:029:18:42:35
Block: 1393580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287616 RingCT/type: yes/0
Extra: 01f519409a58ab3ba491159f1eb150586c58feea5a9ce9b23684cbe3acf0da86be0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 747c2d02f234e631129530665413a10eee19f88f9e48594d57648066e48c1ccb 0.000600000000 1881845 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": 1393590, "vin": [ { "gen": { "height": 1393580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "747c2d02f234e631129530665413a10eee19f88f9e48594d57648066e48c1ccb" } } ], "extra": [ 1, 245, 25, 64, 154, 88, 171, 59, 164, 145, 21, 159, 30, 177, 80, 88, 108, 88, 254, 234, 90, 156, 233, 178, 54, 132, 203, 227, 172, 240, 218, 134, 190, 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: