← previous blocknext block →recent activity
Analyzing
Block #94,674,338
19 transactions · 19 stateful · 2026-08-10 03:59:27 UTC
Parallelism
89/100
Blocked
16%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,674,338 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e182b40…1f35
0x34b655…2a6f
4 touches
1 conflict
0x17c93766…889e
0x34b655…2a6f
4 touches
1 conflict
0x1d0a04dd…b892
0x34b655…2a6f
4 touches
1 conflict
0x27a5809f…7519
0x34b655…2a6f
4 touches
1 conflict
0x2afe51f4…4006
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x65f01a9c…34e0
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
1 conflict on slot 0x0e182b403e…e91f35
Audit this contract →
← previous block·next block →recent activity