← previous blocknext block →recent activity
Analyzing
Block #100,917,483
17 transactions · 11 stateful · 2026-09-01 02:01:07 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,917,483 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6d44d7a7…ee8b
0x065c9d…c394
4 touches
1 conflict
0x129c0db8…a500
0x065c9d…c394
3 touches
1 conflict
0xfdb6e310…0215
0x065c9d…c394
3 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0004
0x63e48b…53f2
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