← previous blocknext block →recent activity
Analyzing
Block #105,471,313
18 transactions · 18 stateful · 2026-09-17 01:13:40 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,471,313 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w18w09w210w313w216w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x100812e9…12b7
0x34b655…2a6f
6 touches
3 conflicts
0x284f8c8e…02d2
0x34b655…2a6f
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x547aec36…7c2b
0x34b655…2a6f
4 touches
1 conflict
0x58b9f942…253d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity