← previous blocknext block →recent activity
Analyzing
Block #108,476,985
16 transactions · 15 stateful · 2026-09-27 13:27:25 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,476,985 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w010w111w312w413w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48203298…65cb
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4f87784c…3a83
0x34b655…2a6f
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0x260229da…080d
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
3 conflicts on slot 0x4820329863…2a65cb
Audit this contract →
← previous block·next block →recent activity