← previous blocknext block →recent activity
Analyzing
Block #100,978,838
19 transactions · 19 stateful · 2026-09-01 07:09:45 UTC
Parallelism
89/100
Blocked
26%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,978,838 · 19 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
1w02w13w04w110w011w113w014w015w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaaf36ccb…f35c
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xcb3ad6d2…f3fe
0x34b655…2a6f
4 touches
1 conflict
0xda50c9d5…674e
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfcae0ed1…0dad
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x51087f5a…61f7
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
1 conflict on slot 0xaaf36ccb41…34f35c
Audit this contract →
← previous block·next block →recent activity