← previous blocknext block →recent activity
Analyzing
Block #108,610,830
19 transactions · 14 stateful · 2026-09-28 00:41:24 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,610,830 · 19 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
1w02w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x80a84411…cd3c
0x34b655…2a6f
4 touches
1 conflict
0xd33a3d56…2ae3
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x3a663e9a…a9c6
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c9
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cc
0x508254…98bd
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 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity