← previous blocknext block →recent activity
Analyzing
Block #106,033,191
16 transactions · 16 stateful · 2026-09-19 00:24:06 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,033,191 · 16 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
1w02w16w09w112w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x52b0bc2b…1305
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8adc194e…b527
0x754704…b603
4 touches
1 conflict
0xc7e70be2…b0c3
0x754704…b603
4 touches
1 conflict
0xf371c34e…e4ac
0x754704…b603
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity