← previous blocknext block →recent activity
Analyzing
Block #100,790,870
30 transactions · 19 stateful · 2026-08-31 15:24:00 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,790,870 · 30 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
1w02w15w06w17w29w010w111w216w217w023w324w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20492d53…80f9
0x34b655…2a6f
6 touches
3 conflicts
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0x8eaf7514…282c
0x34b655…2a6f
6 touches
3 conflicts
0x3c0374a1…932c
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x46abeefb…fc9c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x20492d531d…7380f9
Audit this contract →
← previous block·next block →recent activity