← previous blocknext block →recent activity
Analyzing
Block #107,794,829
31 transactions · 27 stateful · 2026-09-25 04:14:13 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,794,829 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w010w118w019w120w121w022w123w225w327w228w029w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xa64da8fd…bc84
0x40c49f…2af0
5 touches
3 conflicts
0x9420d123…4d0b
0x34b655…2a6f
4 touches
1 conflict
0x98235cbb…7490
0x34b655…2a6f
4 touches
1 conflict
0xa6b55494…76c2
0x34b655…2a6f
4 touches
1 conflict
0xc4d07f57…4f2a
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity