← previous blocknext block →recent activity
Analyzing
Block #107,823,246
31 transactions · 23 stateful · 2026-09-25 06:37:13 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,246 · 31 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
2w03w16w012w113w014w115w216w317w427w029w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41eb76a7…6483
0x34b655…2a6f
10 touches
10 conflicts
0xdcd07321…1c31
0x34b655…2a6f
10 touches
10 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x7c80d7be…b7dc
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xa7ba83b5…d0a8
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 0x41eb76a777…0d6483
Audit this contract →
← previous block·next block →recent activity