← previous blocknext block →recent activity
Analyzing
Block #100,584,978
25 transactions · 24 stateful · 2026-08-30 22:08:07 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,584,978 · 25 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
1w02w03w16w17w08w09w110w111w118w219w020w121w223w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3712b0ac…796c
0x065c9d…c394
5 touches
3 conflicts
0xd9df82d7…549f
0x34b655…2a6f
4 touches
1 conflict
0xdfb56da3…2576
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity