← previous blocknext block →recent activity
Analyzing
Block #106,190,313
16 transactions · 16 stateful · 2026-09-19 13:34:50 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,190,313 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w310w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708d7a74…09e3
0x34b655…2a6f
6 touches
3 conflicts
0x7e18808e…c887
0x34b655…2a6f
4 touches
1 conflict
0x6155be4e…b531
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x62ecdc97…63eb
0x34b655…2a6f
4 touches
1 conflict
0xea504e86…a3ca
0x34b655…2a6f
4 touches
1 conflict
0xfa172c77…3a67
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
3 conflicts on slot 0x708d7a74a7…5d09e3
Audit this contract →
← previous block·next block →recent activity