← previous blocknext block →recent activity
Analyzing
Block #100,611,343
3 transactions · 3 stateful · 2026-08-31 00:20:45 UTC
Parallelism
33/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,611,343 · 3 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50951f37…219c
0x3bd359…433a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13058b25…e212
0x0555e3…2b9c
2 touches
0 conflicts
0xa24d15eb…cc92
0x0555e3…2b9c
2 touches
0 conflicts
0x7bcb8a6b…a34d
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
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: Wrapped MON (WMON)
1 conflict on slot 0x50951f3768…63219c
Audit this contract →
← previous block·next block →recent activity