← previous blocknext block →recent activity
Analyzing
Block #94,848,105
19 transactions · 17 stateful · 2026-08-10 18:35:01 UTC
Parallelism
74/100
Blocked
24%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,848,105 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x324cb18b…bcc6
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3111a64f…eb7f
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x436d1382…f410
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x324cb18bda…b5bcc6
Audit this contract →
← previous block·next block →recent activity