← previous blocknext block →recent activity
Analyzing
Block #100,027,552
22 transactions · 22 stateful · 2026-08-28 23:19:04 UTC
Parallelism
91/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,027,552 · 22 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
1w02w15w08w09w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x2c38ba12…d2e4
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x9a7ab5ce…36e1
0xe52b14…7230
3 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
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: Perpl
1 conflict on slot 0x4f4bdabdf3…ecffba
Audit this contract →
← previous block·next block →recent activity