← previous blocknext block →recent activity
Analyzing
Block #106,383,483
11 transactions · 11 stateful · 2026-09-20 05:47:04 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,383,483 · 11 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
4w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd64c8e10…cd35
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf2
0x4de0d8…bfc3
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7e32f1e0…5612
0x4de0d8…bfc3
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
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: 0x4de0d89d…36bfc3
1 conflict on slot 0xd64c8e10f3…51cd35
Audit this contract →
← previous block·next block →recent activity