← previous blocknext block →recent activity
Analyzing
Block #101,796,957
9 transactions · 7 stateful · 2026-09-04 03:46:01 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,796,957 · 9 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x39f6889c…f92c
0x34b655…2a6f
4 touches
1 conflict
0xb58ed141…c32e
0x34b655…2a6f
4 touches
1 conflict
0xb73a5ffd…ddee
0x34b655…2a6f
4 touches
1 conflict
0xc0f6895c…e428
0x34b655…2a6f
4 touches
1 conflict
0x3cb45e6c…97c0
0x34b655…2a6f
4 touches
1 conflict
0x0729556e…9e71
0x34b655…2a6f
4 touches
1 conflict
0x7daf6443…fd36
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 0x0ffac39e72…c16d34
Audit this contract →
← previous block·next block →recent activity