← previous blocknext block →recent activity
Analyzing
Block #101,491,619
19 transactions · 16 stateful · 2026-09-03 02:10:05 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,491,619 · 19 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
1w08w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x7ed4aa35…24ca
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x26b0fa60…c1cc
0x34b655…2a6f
2 touches
0 conflicts
0x2b7db035…5ed7
0x34b655…2a6f
2 touches
0 conflicts
0x2bea5ce8…3c07
0x34b655…2a6f
2 touches
0 conflicts
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x366a19b0…f065
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 0x22e0cc1d4a…90ad04
Audit this contract →
← previous block·next block →recent activity