← previous blocknext block →recent activity
Analyzing
Block #105,643,867
31 transactions · 28 stateful · 2026-09-17 15:42:10 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,643,867 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w07w18w29w314w121w125w426w529w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf795db…0f13
0x34b655…2a6f
10 touches
10 conflicts
0xa8590d68…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0xb2560305…f27d
0x34b655…2a6f
8 touches
6 conflicts
0x053ba161…98cf
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x62142e5c…a946
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
10 conflicts on slot 0x5cf795db75…680f13
Audit this contract →
← previous block·next block →recent activity