← previous blocknext block →recent activity
Analyzing
Block #102,006,682
19 transactions · 17 stateful · 2026-09-04 21:25:54 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,006,682 · 19 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
2w03w16w07w113w014w116w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ab5ad08…9c6d
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc1da8f73…484c
0x34b655…2a6f
4 touches
1 conflict
0xc9d92517…c787
0x34b655…2a6f
4 touches
1 conflict
0xd07b013b…90cb
0x34b655…2a6f
4 touches
1 conflict
0xebf19faa…72cb
0x34b655…2a6f
4 touches
1 conflict
0xee46716c…d788
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
1 conflict on slot 0x6ab5ad0895…0d9c6d
Audit this contract →
← previous block·next block →recent activity