← previous blocknext block →recent activity
Analyzing
Block #108,483,035
19 transactions · 15 stateful · 2026-09-27 13:57:52 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,483,035 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w210w311w112w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf30b9357…2e1e
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0x797c4391…6833
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xf73dd8a0…fec2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d971bc9…fadc
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 0xf30b935720…582e1e
Audit this contract →
← previous block·next block →recent activity