← previous blocknext block →recent activity
Analyzing
Block #108,476,926
27 transactions · 25 stateful · 2026-09-27 13:27:07 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,476,926 · 27 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
4w05w113w016w118w119w220w321w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ec9dd6b…74b9
0x34b655…2a6f
8 touches
6 conflicts
0xdfd26e5a…9a91
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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
6 conflicts on slot 0x1ec9dd6bf3…ea74b9
Audit this contract →
← previous block·next block →recent activity