← previous blocknext block →recent activity
Analyzing
Block #108,840,056
14 transactions · 12 stateful · 2026-09-28 19:57:35 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,840,056 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3dee8eb4…59c0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3dee8eb4…59c1
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xaf7f13f9…a2c9
0x34b655…2a6f
4 touches
1 conflict
0x91d2ab7a…8ab3
0x34b655…2a6f
4 touches
1 conflict
0x18c1a304…7d9b
0x34b655…2a6f
3 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 0x3dee8eb4d0…2659c0
Audit this contract →
← previous block·next block →recent activity