← previous blocknext block →recent activity
Analyzing
Block #101,800,974
13 transactions · 10 stateful · 2026-09-04 04:06:13 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,800,974 · 13 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81be404d…9716
0x34b655…2a6f
4 touches
1 conflict
0x7ea9d5d4…8219
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xd18b9ae9…9753
0x34b655…2a6f
4 touches
1 conflict
0xe432912b…ceed
0x34b655…2a6f
4 touches
1 conflict
0x22a229ab…5779
0x34b655…2a6f
2 touches
0 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
2 touches
0 conflicts
0x3d13406e…eff1
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 0x81be404d1b…659716
Audit this contract →
← previous block·next block →recent activity