← previous blocknext block →recent activity
Analyzing
Block #100,234,445
28 transactions · 24 stateful · 2026-08-29 16:40:45 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,234,445 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w09w111w012w116w017w118w222w324w425w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8db32935…81a7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x53e5a520…5aac
0x34b655…2a6f
6 touches
3 conflicts
0xbe917242…1b4e
0x34b655…2a6f
6 touches
3 conflicts
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0x5fd61b3c…628d
0x34b655…2a6f
4 touches
1 conflict
0xc4c74438…20e5
0xc8689a…ee79
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity