← previous blocknext block →recent activity
Analyzing
Block #100,021,583
15 transactions · 15 stateful · 2026-08-28 22:49:02 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,021,583 · 15 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
1w02w13w04w16w18w09w110w211w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5748e78d…daff
0x34b655…2a6f
8 touches
6 conflicts
0xfe692697…7723
0x34b655…2a6f
6 touches
3 conflicts
0x341e01be…240c
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
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 0x5748e78da1…b3daff
Audit this contract →
← previous block·next block →recent activity