← previous blocknext block →recent activity
Analyzing
Block #100,748,873
18 transactions · 18 stateful · 2026-08-31 11:52:34 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,748,873 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w09w110w211w312w414w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0xb02035c1…ba92
0x851145…3f07
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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: MarginAccount
10 conflicts on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity