← previous blocknext block →recent activity
Analyzing
Block #108,103,495
16 transactions · 16 stateful · 2026-09-26 06:07:45 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,103,495 · 16 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
7w011w113w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdabae01b…82be
0x34b655…2a6f
4 touches
1 conflict
0xe6fc0ce9…350f
0x34b655…2a6f
4 touches
1 conflict
0x8efe9378…1228
0x065c9d…c394
2 touches
0 conflicts
0x9fc29296…8896
0x065c9d…c394
2 touches
0 conflicts
0xc2b0cb37…8bac
0x065c9d…c394
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity