← previous blocknext block →recent activity
Analyzing
Block #100,895,894
24 transactions · 20 stateful · 2026-09-01 00:12:32 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,895,894 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w16w07w18w09w010w111w116w017w118w221w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87d39100…7270
0x851145…3f07
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5f0a01c3…8269
0x851145…3f07
4 touches
1 conflict
0xb12f39a0…04f1
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x191e0467…70e5
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: 0x851145ea…9f3f07
1 conflict on slot 0x87d3910052…087270
Audit this contract →
← previous block·next block →recent activity