← previous blocknext block →recent activity
Analyzing
Block #102,484,404
25 transactions · 22 stateful · 2026-09-06 13:46:37 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,484,404 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w26w09w110w011w114w015w116w218w219w323w024w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea613003…a4f0
0xe1c8b7…3022
6 touches
3 conflicts
0x3c67d31e…3dbe
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x67d846dd…358c
0x7b6ec4…7777
6 touches
3 conflicts
0x179ef1fb…0e63
0x9f3832…4ae4
6 touches
3 conflicts
0x179ef1fb…0e64
0x9f3832…4ae4
6 touches
3 conflicts
0x1aa4f6ba…439b
0x9f3832…4ae4
6 touches
3 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
6 touches
3 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: 0xe1c8b733…e33022
3 conflicts on slot 0xea613003f3…88a4f0
Audit this contract →
← previous block·next block →recent activity