← previous blocknext block →recent activity
Analyzing
Block #100,605,186
35 transactions · 34 stateful · 2026-08-30 23:49:47 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,605,186 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w08w311w312w013w414w415w117w418w219w020w124w133w034w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6264bbd…cf0b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x35801c67…bcc5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3dc5798b…5c87
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
3 conflicts on slot 0xb6264bbd6d…94cf0b
Audit this contract →
← previous block·next block →recent activity