← previous blocknext block →recent activity
Analyzing
Block #108,517,424
19 transactions · 19 stateful · 2026-09-27 16:51:01 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,517,424 · 19 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
5w06w18w09w111w012w113w114w215w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bf5fe33…250b
0x34b655…2a6f
4 touches
1 conflict
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0x1de20437…05f6
0x34b655…2a6f
4 touches
1 conflict
0x3b659361…89ef
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x532af68d…503d
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 0x0bf5fe33cc…55250b
Audit this contract →
← previous block·next block →recent activity