← previous blocknext block →recent activity
Analyzing
Block #106,565,903
16 transactions · 12 stateful · 2026-09-20 21:05:11 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,565,903 · 16 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
1w02w110w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33303721…96ed
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7e32f1e0…5612
0x4de0d8…bfc3
4 touches
1 conflict
0xd3f1dc40…2578
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf2
0x4de0d8…bfc3
4 touches
1 conflict
0x4856b443…1824
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
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 0x3330372148…d796ed
Audit this contract →
← previous block·next block →recent activity