← previous blocknext block →recent activity
Analyzing
Block #108,493,943
26 transactions · 25 stateful · 2026-09-27 14:52:48 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,493,943 · 26 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
2w03w16w07w18w09w011w114w116w018w119w220w321w422w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8af7cbf3…82be
0x34b655…2a6f
10 touches
10 conflicts
0x74851f5e…fadd
0x34b655…2a6f
10 touches
10 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5bf26b70…28d1
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 0x8af7cbf38d…d882be
Audit this contract →
← previous block·next block →recent activity