← previous blocknext block →recent activity
Analyzing
Block #106,921,731
13 transactions · 13 stateful · 2026-09-22 02:57:07 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,921,731 · 13 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
2w04w05w17w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x4f89250b…4bb2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x27826bde…1da4
0x34b655…2a6f
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
1 conflict on slot 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity