← previous blocknext block →recent activity
Analyzing
Block #108,532,044
15 transactions · 14 stateful · 2026-09-27 18:04:35 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,532,044 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w09w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc856ff11…2b9c
0x34b655…2a6f
4 touches
1 conflict
0xcd0e79e1…4c56
0x34b655…2a6f
4 touches
1 conflict
0xf04bce72…4d3a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0xb64252f2…a7c3
0x34b655…2a6f
4 touches
1 conflict
0x6658fa82…4017
0x754704…b603
2 touches
0 conflicts
0x70a53d84…2d91
0x754704…b603
2 touches
0 conflicts
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 0xc856ff1166…d02b9c
Audit this contract →
← previous block·next block →recent activity