← previous blocknext block →recent activity
Analyzing
Block #106,300,672
10 transactions · 10 stateful · 2026-09-19 22:50:18 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,300,672 · 10 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
1w02w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x26253352…1a75
0x34b655…2a6f
4 touches
1 conflict
0x48b6f2c7…2ef7
0x34b655…2a6f
4 touches
1 conflict
0x4ae38164…15f0
0x34b655…2a6f
4 touches
1 conflict
0x547aec36…7c2b
0x34b655…2a6f
4 touches
1 conflict
0x7499cc33…a306
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
0x34b655…2a6f
4 touches
1 conflict
0x8b7e5c4e…5fae
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 0x1fb8364c98…f7c10d
Audit this contract →
← previous block·next block →recent activity