← previous blocknext block →recent activity
Analyzing
Block #107,442,883
17 transactions · 14 stateful · 2026-09-23 22:40:41 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,442,883 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w110w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf2215806…56d8
0x34b655…2a6f
4 touches
1 conflict
0xf51a94f0…f9b9
0x34b655…2a6f
4 touches
1 conflict
0x5c1cc07a…b400
0x34b655…2a6f
4 touches
1 conflict
0xb25a9e70…cf77
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x37f93b32…cc57
0x34b655…2a6f
4 touches
1 conflict
0xa915ea51…57b0
0x5be4ee…673f
3 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
1 conflict on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity