← previous blocknext block →recent activity
Analyzing
Block #108,501,218
16 transactions · 15 stateful · 2026-09-27 15:29:26 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,501,218 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w011w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59f14360…45d6
0x34b655…2a6f
4 touches
1 conflict
0x9674d680…261b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xccee353a…1cbd
0x34b655…2a6f
4 touches
1 conflict
0xed8224d3…528e
0x34b655…2a6f
4 touches
1 conflict
0x11645e55…c7e5
0x34b655…2a6f
4 touches
1 conflict
0x17c3cde7…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x214b4043…61eb
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 0x59f143600c…ee45d6
Audit this contract →
← previous block·next block →recent activity