← previous blocknext block →recent activity
Analyzing
Block #100,699,413
25 transactions · 22 stateful · 2026-08-31 07:43:45 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,699,413 · 25 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
1w04w05w16w28w013w014w115w117w118w119w020w122w023w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x3dc09507…c195
0x34b655…2a6f
4 touches
1 conflict
0x49cf5413…f268
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x5f46663c…b4c2
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
6 conflicts on slot 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity