← previous blocknext block →recent activity
Analyzing
Block #105,435,635
22 transactions · 20 stateful · 2026-09-16 22:14:08 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,435,635 · 22 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
2w03w14w05w06w17w213w315w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5dac821…b68b
0x34b655…2a6f
8 touches
6 conflicts
0x72c91c95…c636
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0xf46640b0…15bb
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x5b7617d6…60b7
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
6 conflicts on slot 0xb5dac82174…f7b68b
Audit this contract →
← previous block·next block →recent activity