← previous blocknext block →recent activity
Analyzing
Block #94,061,100
19 transactions · 19 stateful · 2026-08-08 00:19:11 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,061,100 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w211w312w413w515w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x539ac47f…eb6f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdedb36e7…3585
0x34b655…2a6f
8 touches
6 conflicts
0xecf5834b…70b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x9927f045…9256
0x34b655…2a6f
6 touches
3 conflicts
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x539ac47ff9…e9eb6f
Audit this contract →
← previous block·next block →recent activity