← previous blocknext block →recent activity
Analyzing
Block #105,881,589
20 transactions · 19 stateful · 2026-09-18 11:40:03 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,881,589 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w010w011w112w213w314w015w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e1bba0c…d8ba
0x34b655…2a6f
8 touches
6 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0xee8237bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x64b18423…c4d0
0x34b655…2a6f
4 touches
1 conflict
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0xcaeee6b1…56a0
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 0x4e1bba0cb3…a3d8ba
Audit this contract →
← previous block·next block →recent activity