← previous blocknext block →recent activity
Analyzing
Block #108,652,694
23 transactions · 12 stateful · 2026-09-28 04:12:15 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,652,694 · 23 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
1w04w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71b64718…0ad1
0x34b655…2a6f
4 touches
1 conflict
0xb88cff0c…8ca0
0x34b655…2a6f
4 touches
1 conflict
0xf5d99816…e2d0
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0x4292a836…9ed5
0x34b655…2a6f
4 touches
1 conflict
0x8d547534…b351
0x065c9d…c394
2 touches
0 conflicts
0x9148e1e4…da11
0x065c9d…c394
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 0x71b64718db…fe0ad1
Audit this contract →
← previous block·next block →recent activity