← previous blocknext block →recent activity
Analyzing
Block #106,576,102
13 transactions · 12 stateful · 2026-09-20 21:56:31 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,576,102 · 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
4w06w18w011w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x8d8bc80a…4276
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
2 touches
0 conflicts
0x8590b692…b267
0x34b655…2a6f
2 touches
0 conflicts
0xca315a97…a519
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity