← previous blocknext block →recent activity
Analyzing
Block #100,919,363
26 transactions · 21 stateful · 2026-09-01 02:10:35 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,919,363 · 26 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
1w02w14w219w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x7391c293…d2d7
0x065c9d…c394
2 touches
0 conflicts
0xe8e599f0…c8d8
0x065c9d…c394
2 touches
0 conflicts
0xf8a54f3d…7210
0x065c9d…c394
2 touches
0 conflicts
0xf8f88d31…fd43
0x065c9d…c394
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity