← previous blocknext block →recent activity
Analyzing
Block #108,533,887
16 transactions · 14 stateful · 2026-09-27 18:13:52 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,533,887 · 16 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x098936f4…836d
0x34b655…2a6f
4 touches
1 conflict
0x0ddc998e…def8
0x34b655…2a6f
4 touches
1 conflict
0x1032f16c…a9b1
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x4c71d355…5ace
0x34b655…2a6f
4 touches
1 conflict
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5acd9e7b…2eb2
0x34b655…2a6f
4 touches
1 conflict
0x6c09658a…d1d9
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 0x098936f4b9…ae836d
Audit this contract →
← previous block·next block →recent activity