← previous blocknext block →recent activity
Analyzing
Block #108,376,205
20 transactions · 20 stateful · 2026-09-27 05:00:11 UTC
Parallelism
90/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,376,205 · 20 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
1w03w15w06w19w010w011w113w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x35006f8a…8e7f
0x34b655…2a6f
4 touches
1 conflict
0x4aa8b305…4ace
0x860869…ff01
4 touches
1 conflict
0x39eca8fb…c49a
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
1 conflict on slot 0xbcdd58ff98…970711
Audit this contract →
← previous block·next block →recent activity