← previous blocknext block →recent activity
Analyzing
Block #106,033,739
17 transactions · 17 stateful · 2026-09-19 00:26:52 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,033,739 · 17 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
1w02w13w05w07w08w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56cb25e3…3e8a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2e618acf…234f
0x754704…b603
4 touches
1 conflict
0x38d5c851…bf46
0x754704…b603
4 touches
1 conflict
0xd0fa1733…0b67
0x754704…b603
4 touches
1 conflict
0x8b71c68e…0f76
0x99c7a7…8bf0
4 touches
1 conflict
0xb0cbcced…df5c
0x99c7a7…8bf0
4 touches
1 conflict
0x4118bd12…924a
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 0x56cb25e375…483e8a
Audit this contract →
← previous block·next block →recent activity