← previous blocknext block →recent activity
Analyzing
Block #105,931,459
21 transactions · 21 stateful · 2026-09-18 15:51:56 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,931,459 · 21 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
1w03w04w05w16w110w211w312w413w314w415w519w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x375b6201…9c1e
0x34b655…2a6f
10 touches
10 conflicts
0x3d73bc02…a363
0x34b655…2a6f
10 touches
10 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
8 touches
6 conflicts
0x05d9b05f…d22c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x045532dd…4b7d
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 0x375b620113…4b9c1e
Audit this contract →
← previous block·next block →recent activity