← previous blocknext block →recent activity
Analyzing
Block #108,300,079
16 transactions · 13 stateful · 2026-09-26 22:37:07 UTC
Parallelism
63/100
Blocked
46%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,300,079 · 16 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
1w08w09w110w211w312w413w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xc4c059d8…185d
0x34b655…2a6f
6 touches
3 conflicts
0x39503f6f…3a4d
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x7c6ffab4…d7c3
0x34b655…2a6f
4 touches
1 conflict
0x6ae5284d…8fa7
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 0x5e2ea201dc…2012de
Audit this contract →
← previous block·next block →recent activity