← previous blocknext block →recent activity
Analyzing
Block #108,468,113
16 transactions · 14 stateful · 2026-09-27 12:42:46 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,468,113 · 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
1w02w03w16w17w011w112w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69bb4e1…f2bb
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x84ca2a4a…ab8e
0x34b655…2a6f
4 touches
1 conflict
0x5bfd5d4d…1d53
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 0xa69bb4e112…87f2bb
Audit this contract →
← previous block·next block →recent activity