← previous blocknext block →recent activity
Analyzing
Block #100,728,468
13 transactions · 12 stateful · 2026-08-31 10:09:56 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,728,468 · 13 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
5w07w18w29w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34fe25fc…0293
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xf4497fd3…6ff0
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
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 0x34fe25fcc8…a30293
Audit this contract →
← previous block·next block →recent activity