← previous blocknext block →recent activity
Analyzing
Block #102,019,216
8 transactions · 8 stateful · 2026-09-04 22:29:19 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,019,216 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc852b267…9d14
0x34b655…2a6f
6 touches
3 conflicts
0x247cfb80…cca8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0xd5f4e613…6ca9
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0010
0x2358b9…5037
2 touches
0 conflicts
0x915ce213…4c99
0x2358b9…5037
2 touches
0 conflicts
0xca5843d9…4436
0x2358b9…5037
2 touches
0 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
3 conflicts on slot 0xc852b26715…339d14
Audit this contract →
← previous block·next block →recent activity