← previous blocknext block →recent activity
Analyzing
Block #100,723,627
11 transactions · 9 stateful · 2026-08-31 09:45:35 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,723,627 · 11 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
1w02w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc1a333b9…ab45
0x34b655…2a6f
4 touches
1 conflict
0xc1b89907…8134
0x34b655…2a6f
4 touches
1 conflict
0x260cc5c4…bef0
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1869
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186a
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…186d
0x34ae4d…3fc5
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 0xfc24540b5d…4d6463
Audit this contract →
← previous block·next block →recent activity