← previous blocknext block →recent activity
Analyzing
Block #100,748,843
19 transactions · 19 stateful · 2026-08-31 11:52:25 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,748,843 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w39w110w211w312w413w514w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8fcee65…7710
0x851145…3f07
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x73912233…4583
0x1b6862…e19c
8 touches
6 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: 0x851145ea…9f3f07
15 conflicts on slot 0xb8fcee651e…a97710
Audit this contract →
← previous block·next block →recent activity