← previous blocknext block →recent activity
Analyzing
Block #100,117,337
23 transactions · 22 stateful · 2026-08-29 06:51:06 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,117,337 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w113w217w319w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x3fead0ae…0e35
0x34b655…2a6f
4 touches
1 conflict
0x45885570…ed97
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50f2372e…df46
0x34b655…2a6f
4 touches
1 conflict
0x5f46663c…b4c2
0x34b655…2a6f
4 touches
1 conflict
0x852fd1a4…8169
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
3 conflicts on slot 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity