← previous blocknext block →recent activity
Analyzing
Block #100,144,599
10 transactions · 9 stateful · 2026-08-29 09:08:29 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,144,599 · 10 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb44
0x34b655…2a6f
4 touches
1 conflict
0xdfe6bc89…042e
0x34b655…2a6f
4 touches
1 conflict
0xb8f61e91…35e7
0x34b655…2a6f
4 touches
1 conflict
0x24f8d031…2187
0x34b655…2a6f
2 touches
0 conflicts
0x2f4b1dc8…e9fa
0x34b655…2a6f
2 touches
0 conflicts
0x3d7625a2…1c1b
0x34b655…2a6f
2 touches
0 conflicts
0x610e0337…4f23
0x34b655…2a6f
2 touches
0 conflicts
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 0x65e6e6031f…4fcb45
Audit this contract →
← previous block·next block →recent activity