← previous blocknext block →recent activity
Analyzing
Block #101,491,868
14 transactions · 13 stateful · 2026-09-03 02:11:20 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,491,868 · 14 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
1w03w04w15w09w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56ae218…1fc5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0xa3367d00…4960
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x21e8ab54…3b4b
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 0xa56ae21853…e31fc5
Audit this contract →
← previous block·next block →recent activity