← previous blocknext block →recent activity
Analyzing
Block #100,700,910
24 transactions · 22 stateful · 2026-08-31 07:51:17 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,700,910 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w014w115w216w017w118w219w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x451e482b…7e7d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x63aac9e4…d50a
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity