← previous blocknext block →recent activity
Analyzing
Block #108,641,141
24 transactions · 21 stateful · 2026-09-28 03:14:05 UTC
Parallelism
92/100
Blocked
14%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,641,141 · 24 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
7w08w113w014w018w019w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb991f1e1…5e32
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x37f93b32…cc57
0x34b655…2a6f
4 touches
1 conflict
0x88946e9f…2bcc
0x34b655…2a6f
4 touches
1 conflict
0x8b780b26…f5ff
0x34b655…2a6f
4 touches
1 conflict
0x17284c65…ee9f
0x34b655…2a6f
2 touches
0 conflicts
0x59063527…7864
0x34b655…2a6f
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 0xb991f1e19a…0c5e32
Audit this contract →
← previous block·next block →recent activity