← previous blocknext block →recent activity
Analyzing
Block #91,076,160
43 transactions · 36 stateful · 2026-07-28 14:01:02 UTC
Parallelism
91/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,076,160 · 43 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w18w09w110w211w313w014w121w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc55c9f75…aea7
0x065c9d…c394
4 touches
1 conflict
0xefc8cee6…4474
0x065c9d…c394
4 touches
1 conflict
0xf62ea3fd…3f6f
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: MarginAccount
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity