← previous blocknext block →recent activity
Analyzing
Block #108,619,746
24 transactions · 20 stateful · 2026-09-28 01:26:18 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,619,746 · 24 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
1w03w14w08w09w110w211w315w116w017w118w119w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x55a37f69…aece
0x34b655…2a6f
6 touches
3 conflicts
0x724ba0cf…01c7
0x34b655…2a6f
6 touches
3 conflicts
0x1321736a…43e3
0x34b655…2a6f
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x1a99f155…77b7
0x34b655…2a6f
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
4 touches
1 conflict
0x399a45fd…1312
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity