← previous blocknext block →recent activity
Analyzing
Block #100,430,879
16 transactions · 14 stateful · 2026-08-30 09:12:49 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,430,879 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
13w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3abe489…ebf3
0x6eb2af…2f9a
4 touches
1 conflict
0x0fd2cbc5…476b
0x6eb2af…2f9a
4 touches
1 conflict
0x4b7c8acb…9de2
0x6eb2af…2f9a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0547420b…fc46
0x34b655…2a6f
2 touches
0 conflicts
0x451e482b…7e7d
0x34b655…2a6f
2 touches
0 conflicts
0x958fee6b…80a8
0x34b655…2a6f
2 touches
0 conflicts
0xa92c8763…6d7f
0x34b655…2a6f
2 touches
0 conflicts
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: 0x6eb2af5f…1a2f9a
1 conflict on slot 0xe3abe4895e…e5ebf3
Audit this contract →
← previous block·next block →recent activity