← previous blocknext block →recent activity
Analyzing
Block #106,413,313
15 transactions · 13 stateful · 2026-09-20 08:17:10 UTC
Parallelism
87/100
Blocked
15%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,413,313 · 15 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
1w010w011w112w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9364140…7f2c
0x34b655…2a6f
4 touches
1 conflict
0x98dd86bb…1edb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
0x34b655…2a6f
2 touches
0 conflicts
0x556beb43…e627
0x34b655…2a6f
2 touches
0 conflicts
0x74cdc294…26a8
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 0xb936414081…c57f2c
Audit this contract →
← previous block·next block →recent activity