← previous blocknext block →recent activity
Analyzing
Block #108,654,153
26 transactions · 20 stateful · 2026-09-28 04:19:35 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,654,153 · 26 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
4w05w19w010w111w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x6f42fec4…4d4a
0x34b655…2a6f
4 touches
1 conflict
0xe8770881…2e82
0x34b655…2a6f
4 touches
1 conflict
0xbfd56fdb…41c9
0x34b655…2a6f
4 touches
1 conflict
0xc856ff11…2b9c
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity