← previous blocknext block →recent activity
Analyzing
Block #106,381,450
15 transactions · 14 stateful · 2026-09-20 05:36:49 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,381,450 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f1ffb67…59a2
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x4068d9ca…5fc5
0x34b655…2a6f
4 touches
1 conflict
0xd2c5fb75…6c9b
0x34b655…2a6f
4 touches
1 conflict
0xe8058ec4…ebac
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
1 conflict on slot 0x5f1ffb67aa…7159a2
Audit this contract →
← previous block·next block →recent activity