← previous blocknext block →recent activity
Analyzing
Block #108,567,299
24 transactions · 23 stateful · 2026-09-27 21:02:16 UTC
Parallelism
92/100
Blocked
4%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,567,299 · 24 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed5edd21…eecd
0x34b655…2a6f
4 touches
1 conflict
0x80eae3b5…8de7
0x34b655…2a6f
4 touches
1 conflict
0x221e8974…2a9a
0x34b655…2a6f
4 touches
1 conflict
0xe763a93c…e90b
0x34b655…2a6f
4 touches
1 conflict
0x1aa85bda…e324
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x3e49348b…9445
0x34b655…2a6f
2 touches
0 conflicts
0x56e0948c…5a34
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 0xed5edd2137…88eecd
Audit this contract →
← previous block·next block →recent activity