← previous blocknext block →recent activity
Analyzing
Block #108,927,502
33 transactions · 17 stateful · 2026-09-29 03:18:52 UTC
Parallelism
79/100
Blocked
65%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,927,502 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w012w114w215w317w418w020w121w222w323w527w429w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x06e40499…165e
0x34ae4d…3fc5
10 touches
10 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
10 touches
10 conflicts
0x15698ac9…2a46
0x34b655…2a6f
10 touches
10 conflicts
0x199a4f01…2183
0x34b655…2a6f
10 touches
10 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity