← previous blocknext block →recent activity
Analyzing
Block #108,619,600
14 transactions · 14 stateful · 2026-09-28 01:25:34 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,619,600 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cf51b60…2fdd
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51162fee…d428
0x34b655…2a6f
4 touches
1 conflict
0xc856ff11…2b9c
0x34b655…2a6f
4 touches
1 conflict
0xd9477d67…dd9a
0x34b655…2a6f
4 touches
1 conflict
0xdd151569…fcc5
0x34b655…2a6f
4 touches
1 conflict
0xe7e6031b…b25d
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 0x1cf51b60ac…c02fdd
Audit this contract →
← previous block·next block →recent activity