← previous blocknext block →recent activity
Analyzing
Block #100,918,399
16 transactions · 13 stateful · 2026-09-01 02:05:44 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,918,399 · 16 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
1w02w112w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb000e84a…e68c
0x065c9d…c394
4 touches
1 conflict
0xfe0fd8aa…7595
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8dcb539c…caa9
0x065c9d…c394
3 touches
1 conflict
0xe4febfaa…cf6a
0x065c9d…c394
3 touches
1 conflict
0x9510a6cd…fd5b
0x065c9d…c394
3 touches
1 conflict
0x208db61e…b33d
0x065c9d…c394
3 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
1 conflict on slot 0xb000e84adb…76e68c
Audit this contract →
← previous block·next block →recent activity