← previous blocknext block →recent activity
Analyzing
Block #108,397,233
17 transactions · 16 stateful · 2026-09-27 06:46:00 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,397,233 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w111w012w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2c60983b…3244
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity