← previous blocknext block →recent activity
Analyzing
Block #108,404,228
18 transactions · 16 stateful · 2026-09-27 07:21:12 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,404,228 · 18 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
1w02w14w011w013w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0x1679b727…0208
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a1
0x34b655…2a6f
2 touches
0 conflicts
0xaba6578d…bd48
0x34b655…2a6f
2 touches
0 conflicts
0xdb3937e8…23cb
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 0xba9f9225da…4d2ead
Audit this contract →
← previous block·next block →recent activity