← previous blocknext block →recent activity
Analyzing
Block #106,045,968
13 transactions · 12 stateful · 2026-09-19 01:28:24 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,045,968 · 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
2w09w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fc536fb…1aa1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x2f66b459…ddbe
0x34b655…2a6f
2 touches
0 conflicts
0x32928f68…2345
0x34b655…2a6f
2 touches
0 conflicts
0x3e31ac12…a5f0
0x34b655…2a6f
2 touches
0 conflicts
0x6435bd34…b160
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 0x0fc536fb1f…c81aa1
Audit this contract →
← previous block·next block →recent activity