← previous blocknext block →recent activity
Analyzing
Block #108,988,876
19 transactions · 15 stateful · 2026-09-29 08:29:22 UTC
Parallelism
84/100
Blocked
20%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,988,876 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008d910c…0bde
0x34b655…2a6f
4 touches
1 conflict
0x0d54fa3e…3b3c
0x34b655…2a6f
4 touches
1 conflict
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x1c414c9c…ccc1
0x34b655…2a6f
4 touches
1 conflict
0x3b99565b…6441
0x34b655…2a6f
4 touches
1 conflict
0x3e1124f3…1035
0x34b655…2a6f
4 touches
1 conflict
0x466771e2…9731
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
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
1 conflict on slot 0x008d910c89…250bde
Audit this contract →
← previous block·next block →recent activity