← previous blocknext block →recent activity
Analyzing
Block #106,027,878
17 transactions · 16 stateful · 2026-09-18 23:57:22 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,027,878 · 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
2w03w16w09w114w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x08f9abf1…10bf
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4ee0b65a…6d40
0x34b655…2a6f
4 touches
1 conflict
0xbb95fb3e…c47b
0x754704…b603
2 touches
0 conflicts
0xf4d134b9…d866
0x754704…b603
2 touches
0 conflicts
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 0x502b3ee1e6…227f7c
Audit this contract →
← previous block·next block →recent activity