← previous blocknext block →recent activity
Analyzing
Block #107,823,553
31 transactions · 25 stateful · 2026-09-25 06:38:46 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,553 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w111w212w313w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2c4d203…05b6
0x34b655…2a6f
8 touches
6 conflicts
0xa8753ff9…2a9f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
6 touches
3 conflicts
0x232b0b19…d946
0x34b655…2a6f
6 touches
3 conflicts
0x90d24713…b88f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0e7a2213…4407
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 0xa2c4d203df…b805b6
Audit this contract →
← previous block·next block →recent activity