← previous blocknext block →recent activity
Analyzing
Block #102,078,709
18 transactions · 17 stateful · 2026-09-05 03:30:54 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,078,709 · 18 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
1w02w13w24w05w16w27w313w015w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
8 touches
6 conflicts
0xc52785b9…08f8
0x34b655…2a6f
8 touches
6 conflicts
0xd2fb0612…5edf
0x34b655…2a6f
8 touches
6 conflicts
0xd98afa6e…3364
0x34b655…2a6f
8 touches
6 conflicts
0xdec2aeb2…0586
0x34b655…2a6f
8 touches
6 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
8 touches
6 conflicts
0x01315072…0e2d
0x34b655…2a6f
8 touches
6 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xfd713bab1a…98a651
Audit this contract →
← previous block·next block →recent activity