← previous blocknext block →recent activity
Analyzing
Block #100,268,470
21 transactions · 15 stateful · 2026-08-29 19:33:29 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,268,470 · 21 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
9w010w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc82b8d1f…45ff
0x34b655…2a6f
4 touches
1 conflict
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0xee757899…302b
0x34b655…2a6f
4 touches
1 conflict
0x51f32324…de5c
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
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
1 conflict on slot 0xc82b8d1f17…ca45ff
Audit this contract →
← previous block·next block →recent activity