← previous blocknext block →recent activity
Analyzing
Block #100,577,284
26 transactions · 24 stateful · 2026-08-30 21:29:25 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,577,284 · 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
2w03w16w08w09w010w111w213w114w320w424w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x820d7282…6c34
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x4c0f4f48…d9b7
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x73328085…275d
0x34b655…2a6f
4 touches
1 conflict
0x7b8b5ba9…7ab9
0x34b655…2a6f
4 touches
1 conflict
0xa8471c8a…0fc1
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 0x820d72829e…536c34
Audit this contract →
← previous block·next block →recent activity