← previous blocknext block →recent activity
Analyzing
Block #100,729,062
18 transactions · 17 stateful · 2026-08-31 10:12:55 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,729,062 · 18 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
3w04w114w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x37af32af…36c0
0x34b655…2a6f
2 touches
0 conflicts
0x382434ca…96b5
0x34b655…2a6f
2 touches
0 conflicts
0x38d6111f…33a0
0x34b655…2a6f
2 touches
0 conflicts
0x5b3e008a…4aa9
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity