← previous blocknext block →recent activity
Analyzing
Block #100,618,394
16 transactions · 14 stateful · 2026-08-31 00:56:13 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,618,394 · 16 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
3w08w112w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40d34bb6…715f
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
4 touches
1 conflict
0x5e8223c2…c242
0x34b655…2a6f
2 touches
0 conflicts
0x68dbf226…a256
0x34b655…2a6f
2 touches
0 conflicts
0x6d105005…3cc9
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
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 0x40d34bb671…7b715f
Audit this contract →
← previous block·next block →recent activity