← previous blocknext block →recent activity
Analyzing
Block #106,018,038
14 transactions · 14 stateful · 2026-09-18 23:07:51 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,018,038 · 14 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
1w02w16w28w010w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xb40e601f…bf98
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0fb20484…1982
0x34b655…2a6f
4 touches
1 conflict
0x03b73495…892d
0x065c9d…c394
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity