← previous blocknext block →recent activity
Analyzing
Block #100,129,465
19 transactions · 16 stateful · 2026-08-29 07:52:09 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,129,465 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w113w014w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b4018a7…8c7d
0x8964d7…10f8
6 touches
3 conflicts
0x4b4018a7…8c7a
0x8964d7…10f8
6 touches
3 conflicts
0x4b4018a7…8c80
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x4b4018a7…8c79
0x8964d7…10f8
6 touches
3 conflicts
0x4b4018a7…8c7e
0x8964d7…10f8
6 touches
3 conflicts
0xc01af9ad…179c
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x4b4018a76a…768c7d
Audit this contract →
← previous block·next block →recent activity