← previous blocknext block →recent activity
Analyzing
Block #100,923,097
26 transactions · 22 stateful · 2026-09-01 02:29:22 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,923,097 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w215w016w117w218w320w424w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52ff77fc…1085
0x34b655…2a6f
10 touches
10 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
10 touches
10 conflicts
0x50b85fab…26e4
0x34b655…2a6f
8 touches
6 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xef3f5637…f47c
0x34b655…2a6f
6 touches
3 conflicts
0x0f376ada…b4ec
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
10 conflicts on slot 0x52ff77fc3f…011085
Audit this contract →
← previous block·next block →recent activity