← previous blocknext block →recent activity
Analyzing
Block #100,704,493
17 transactions · 15 stateful · 2026-08-31 08:09:18 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,704,493 · 17 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
1w02w17w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x7deb183c…0858
0x34b655…2a6f
3 touches
1 conflict
0xf66bf5ca…1b95
0x065c9d…c394
3 touches
1 conflict
0x495a2032…0231
0x065c9d…c394
2 touches
0 conflicts
0x7d381880…b0f0
0x065c9d…c394
2 touches
0 conflicts
0xde562941…017a
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity